74
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Deepbook V3
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
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
60
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under Apache-2.0.
Engineering
77
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
CI is configured (.github/workflows/deepbookv3-build-tx.yml).
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (.claude/skills/predict-audit/evals/test_consolidate_track.py).
Linter or formatter configured (packages/.prettierrc).
Project health
89
Dependency manifest found (Cargo.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
- 22 / 112Commits (30d / 90d)
- 92Forks
- 0Releases
Community
- 37% - WeakCommunity health
- -authors own >50% of commits
- 202Watchers
Responsiveness
- 2d 8hMedian issue response
- <1hMedian PR merge time
- 10Open issues
Repository files20 root entries
- .claudeGood: Test files detected (.claude/skills/predict-audit/evals/test_consolidate_track.py).
- .githubGood: CI is configured (.github/workflows/deepbookv3-build-tx.yml).
- crates
- dockerGood: Environment pinned via docker/deepbook-indexer/Dockerfile.
- docs
- packagesGood: Linter or formatter configured (packages/.prettierrc).
- scripts
- .gitignoreGood: .gitignore present.
- AGENTS.md
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CLAUDE.md
- DBv3Architecture.png
- DeepBook Governance Timeline.png
- DeepBook_Logo_White.png
- LICENSEGood: Licensed under Apache-2.0.
- package.json
- pnpm-lock.yaml
- pnpm-workspace.yaml
- README.mdGood: 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.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.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/mystenlabs/deepbookv3)