sherlock-project/sherlock vs sjmoran/yc-ai-cohort-analysis
sherlock-project/sherlock shows stronger signals overall
As of June 2026, sherlock shows healthier maintenance signals than yc-ai-cohort-analysis. sherlock rates Healthy overall while yc-ai-cohort-analysis rates Mixed. sherlock was committed to 1 day ago with 24+ active contributors, while yc-ai-cohort-analysis last saw a commit 2 months ago with 1+ active contributor. Both use the MIT license. 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.
sherlock-project/sherlock →
Healthy across the board
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
No critical CVEs, sane security posture — runnable as-is.
- ✓Last commit today
- ✓24+ active contributors
- ✓Distributed ownership (top contributor 32% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
sjmoran/yc-ai-cohort-analysis →
Solo project — review before adopting
single-maintainer (no co-maintainers visible); no tests detected…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; no CI workflows detected
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠No CI workflows detected
- ⚠No test directory detected
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 4w ago
- ✓MIT licensed
What would improve this?
- →Use as dependency Mixed → Healthy if: onboard a second core maintainer; add a test suite
- →Deploy as-is Mixed → Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
Signal-by-signal breakdown
| sherlock | yc-ai-cohort-analysis | |
|---|---|---|
| Stars | 85,525 | 0 |
| Last commit | 1d ago | 2mo ago |
| License | MIT | MIT |
| Open issues | 299 | 0 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 100% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | A | A |
| Cycles | 0 | 0 |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? sherlock-project/sherlock · sjmoran/yc-ai-cohort-analysis
Ask AI about sherlock-project/sherlock vs sjmoran/yc-ai-cohort-analysis
Open the chat with a comparison question pre-filled.