kitware/vtk

0

/ 100

Documentation43
Engineering90
Health100
C++3,167Other1d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

Mirror of Visualization Toolkit repository

Documentation

43

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt40

README is present.

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

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

License6pt100

Licensed under Other.

Engineering

90

Tests18pt80

Test files detected (CMake/wheel_sdks/tests).

Reproducibility6pt80

Lockfile present (.gitlab/ci/requirements.txt). Installs are reproducible.

CI/CD14pt100

CI is configured (.gitlab-ci.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (.gitlab/ci/requirements.txt).

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)
  • 1,298
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 3,167
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files48 root entries
  • .ExternalData
  • .github
    Good: Issue or PR templates present.
  • .gitlab
    Good: Lockfile present (.gitlab/ci/requirements.txt). Installs are reproducible.
    Good: Environment pinned via .gitlab/ci/docker/el7-mindeps/Dockerfile.
    Good: Dependency manifest found (.gitlab/ci/requirements.txt).
  • Accelerators
    Good: Licensed under Other.
  • Charts
  • CMake
    Good: Test files detected (CMake/wheel_sdks/tests).
  • Common
  • Documentation
  • Domains
  • Examples
  • Filters
  • Geovis
  • GUISupport
  • Imaging
  • Infovis
  • Interaction
  • IO
  • Parallel
  • Remote
  • Rendering
  • Serialization
  • Testing
  • ThirdParty
  • Utilities
  • Views
  • Web
  • Wrapping
  • .clang-format
  • .clang-tidy
  • .codespellrc
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .editorconfig-checker.json
  • .git-remote-files
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
    Good: CI is configured (.gitlab-ci.yml).
  • .hooks-config.bash
  • .kitware-release-paraview.json
  • .kitware-release.json
  • .readthedocs.yaml
  • CMakeLists.txt
  • CMakePresets.json
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • Copyright.txt
  • CTestConfig.cmake
  • README.md
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • vtkBanner.gif
  • vtkLogo.ico