microsoft/swin-transformer vs sherlock-project/sherlock
sherlock-project/sherlock shows stronger signals overall
As of June 2026, sherlock shows healthier maintenance signals than swin-transformer. sherlock rates Healthy overall while swin-transformer rates Mixed. swin-transformer last saw a commit 1 year ago with 14+ active contributors, while sherlock was committed to 1 day ago with 24+ active contributors. 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.
microsoft/swin-transformer →
Stale — last commit 2y ago
last commit was 2y ago; no tests detected…
Has a license, tests, and CI — clean foundation to fork and modify.
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
- ⚠No CI workflows detected
- ⚠No test directory detected
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓14 active contributors
- ✓Distributed ownership (top contributor 40% of recent commits)
- ✓MIT licensed
What would improve this?
- →Use as dependency Mixed → Healthy if: 1 commit in the last 365 days; add a test suite
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days; 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
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
Signal-by-signal breakdown
| swin-transformer | sherlock | |
|---|---|---|
| Stars | 15,902 | 85,525 |
| Last commit | 1y ago | 1d ago |
| License | MIT | MIT |
| Open issues | 204 | 299 |
| Has tests | — | ✓ |
| Has CI | — | ✓ |
| Test coverage | 0% | 100% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | A |
| Cycles | — | 0 |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? microsoft/swin-transformer · sherlock-project/sherlock
Ask AI about microsoft/swin-transformer vs sherlock-project/sherlock
Open the chat with a comparison question pre-filled.