insightsoftwareconsortium/itk

0

/ 100

Documentation87
Engineering83
Health86
C++1,628Apache-2.01d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

Insight Toolkit (ITK) -- Official Repository. ITK builds on a proven, spatially-oriented architecture for processing, segmentation, and registration of scientific images in two, three, or more dimensions.

Documentation

87

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt93

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

83

Reproducibility6pt70

Lockfile present (Documentation/docs/requirements.txt). Installs are reproducible.

CI/CD14pt72

CI is configured (.github/workflows/pre-commit.yml).

Tests18pt85

Test files detected (Examples/DataRepresentation/Image/test).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (pyproject.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 735
    Forks
  • 42
    Releaseslatest 7y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,628
    Watchers

Responsiveness

  • 1d 10h
    Median issue response
  • 3d 12h
    Median PR merge time
  • 289
    Open issues
Repository files36 root entries
  • .ExternalData
  • .github
    Good: CI is configured (.github/workflows/pre-commit.yml).
    Good: Issue or PR templates present.
  • CMake
  • Documentation
    Good: Lockfile present (Documentation/docs/requirements.txt). Installs are reproducible.
  • Examples
    Good: Test files detected (Examples/DataRepresentation/Image/test).
  • Modules
  • Testing
  • Utilities
  • Wrapping
  • .clang-format
  • .clang-tidy
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gersemi.config
  • .git-blame-ignore-revs
  • .git-remote-files
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • .pre-commit-config.yaml
  • .readthedocs.yml
  • .zenodo.json
  • AGENTS.md
  • CITATION.cff
  • CLAUDE.md
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • CTestConfig.cmake
  • GettingStarted.md
  • GOVERNANCE.md
  • greptile.json
  • LICENSE
    Good: Licensed under Apache-2.0.
  • NOTICE
  • pixi.lock
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.