visit-dav/visit

0

/ 100

Documentation58
Engineering69
Health100
C520BSD-3-Clause1d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

VisIt - Visualization and Data Analysis for Mesh-based Scientific Data

Documentation

58

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

Contributing guide5pt47

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.

README12pt85

README is present.

License6pt100

Licensed under BSD-3-Clause.

Engineering

69

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

CI/CD14pt57

CI is configured (.github/workflows/build_visit_tpls.yaml).

Tests18pt80

Test files detected (scripts/docker/test_visit.py).

Reproducibility6pt92

Lockfile present (src/doc/requirements.txt). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (src/doc/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)
  • 137
    Forks
  • 24
    Releaseslatest 6y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 520
    Watchers

Responsiveness

  • 23h
    Median issue response
  • <1h
    Median PR merge time
  • 1,943
    Open issues
Repository files18 root entries
  • .github
    Good: CI is configured (.github/workflows/build_visit_tpls.yaml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • data
  • docs
  • scripts
    Good: Test files detected (scripts/docker/test_visit.py).
    Good: Environment pinned via scripts/ci/docker/Dockerfile.
  • src
    Good: Lockfile present (src/doc/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (src/doc/requirements.txt).
  • test
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .readthedocs.yaml
  • azure-pipelines.yml
  • CITATION.cff
  • 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.
  • hashes.txt
  • LICENSE
    Good: Licensed under BSD-3-Clause.
  • NOTICE
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Good: README includes status badges.
    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.
  • SECURITY.md
    Good: Security policy present.