chroma-core/chroma vs cozodb/cozo
chroma-core/chroma shows stronger signals overall
As of September 2026, chroma shows healthier maintenance signals than cozo. chroma rates Healthy overall while cozo rates Mixed. chroma was committed to 1 week ago with 9+ active contributors, while cozo last saw a commit 1 year ago with 15+ active contributors. chroma is Apache-2.0-licensed while cozo is MPL-2.0-licensed. Neither has known critical or high-severity CVEs in its dependency tree.
Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.
chroma-core/chroma
Strong maintenance signals
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Token-Permissions" is 0/10; 8 cyclic import chains — pervasive coupling
- ✓Last commit today
- ✓9 active contributors
- ✓Distributed ownership (top contributor 41% of recent commits)
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: bring "Token-Permissions" to ≥3/10 (see scorecard report)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
cozodb/cozo
Stale — last commit 2y ago
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; Scorecard "Branch-Protection" is 0/10
- ⚠Stale — last commit 2y ago
- ⚠Concentrated ownership — top contributor handles 72% of recent commits
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓15 active contributors
- ✓MPL-2.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
Signal-by-signal breakdown
| chroma | cozo | |
|---|---|---|
| Stars | 29,219 | 4,104 |
| Last commit | 9d ago | 1y ago |
| License | Apache-2.0 | MPL-2.0 |
| Open issues | 823 | 50 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 33% | 9% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | A |
| Cycles | 8 | 0 |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? chroma-core/chroma · cozodb/cozo
Ask AI about chroma-core/chroma vs cozodb/cozo
Open the chat with a comparison question pre-filled.