0
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
Deep probabilistic analysis of single-cell and spatial omics data
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
78
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under BSD-3-Clause.
Engineering
85
No dependency lockfile found (−70 pts).
→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.
CI is configured (.github/workflows/build_image_base.yaml).
Test files detected (conftest.py).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
98
Dependency manifest found (pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 465Forks
- 94Releaseslatest 5y ago
Community
- -Community health
- -authors own >50% of commits
- 1,650Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 28Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/build_image_base.yaml).Good: Issue or PR templates present.
- docs
- src
- tests
- .codecov.yaml
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .gitmodules
- .markdownlint.yaml
- .pre-commit-config.yaml
- .readthedocs.yaml
- CHANGELOG.md
- conftest.pyGood: Test files detected (conftest.py).
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSEGood: Licensed under BSD-3-Clause.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: 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.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.Good: README documents how to install the project.Good: README documents how to run the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/scverse/scvi-tools)