Good shape overall. A few tweaks would push it into the top tier.
Deepbook V3
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 (crates/indexer/tests).
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
- —Commits (30d / 90d)
- 91Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 201Watchers
Responsiveness
- 2d 8hMedian issue response
- <1hMedian PR merge time
- 11Open issues
Repository files21 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/deepbookv3-build-tx.yml).
- cratesGood: Test files detected (crates/indexer/tests).
- 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.
- rule-auditor.md