sherlock-project/sherlock vs wting/autojump
sherlock-project/sherlock shows stronger signals overall
As of June 2026, sherlock shows healthier maintenance signals than autojump. sherlock rates Healthy overall while autojump rates Mixed. sherlock was committed to 1 day ago with 24+ active contributors, while autojump last saw a commit 1 year ago with 13+ active contributors. sherlock is MIT-licensed while autojump is Other-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.
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
wting/autojump →
Stale — last commit 1y ago
non-standard license (Other); last commit was 1y ago
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 1y ago; Scorecard "Branch-Protection" is 0/10
- ⚠Stale — last commit 1y ago
- ⚠Single-maintainer risk — top contributor 82% of recent commits
- ⚠Non-standard license (Other) — review terms
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓13 active contributors
- ✓Other licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
- →Deploy as-is Mixed → 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 OpenSSF Scorecard
Signal-by-signal breakdown
| sherlock | autojump | |
|---|---|---|
| Stars | 85,525 | 16,906 |
| Last commit | 1d ago | 1y ago |
| License | MIT | Other |
| Open issues | 299 | 230 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 100% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | A | — |
| Cycles | 0 | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? sherlock-project/sherlock · wting/autojump
Ask AI about sherlock-project/sherlock vs wting/autojump
Open the chat with a comparison question pre-filled.