vgteam/vg
Grade a repo

78

/ 100

GradeB

Well engineered. The main gaps are CI and linting.

Top 28% of 5,156 graded repos

tools for working with genome variation graphs

Documentation93
Engineering68
Health100
C++1,333Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

93

Contributing guide5pt76

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

68

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/testmac.yml).

Tests18pt80

Test files detected (pytest.ini).

Reproducibility6pt80

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (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

  • 85 / 488
    Commits (30d / 90d)
  • 219
    Forks
  • 88
    Releaseslatest 8y ago

Community

  • 62% - Fair
    Community health
  • 3 bus factor
    authors own >50% of commits
  • 1,333
    Watchers

Responsiveness

  • 12d 22h
    Median issue response
  • 1d 20h
    Median PR merge time
  • 400
    Open issues
Repository files28 root entries
  • .github
    Good: CI is configured (.github/workflows/testmac.yml).
    Good: Issue or PR templates present.
  • contrib
  • deps
  • doc
    Good: Lockfile present (doc/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (doc/requirements.txt).
  • ontology
  • scripts
  • src
  • test
  • vgci
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
  • .gitmodules
  • autocomp.bash
  • autocomplete.sh
  • BOTS.md
  • Brewfile
  • CLAUDE.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
    Good: Contributing guide includes code examples.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.static
  • Doxyfile
  • LICENSE
    Good: Licensed under Other.
  • Makefile
  • pre-build.sh
  • pytest.ini
    Good: Test files detected (pytest.ini).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
  • source_me.sh
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/vgteam/vg)](https://www.repo-grade.com/report/vgteam/vg)

More graded C++ repos