halo-dev/halo vs pqpo/smartcropper
Both showing Mixed signals — pick on fit, not health
As of September 2026, halo and smartcropper both show mixed maintenance signals. halo was committed to 2 weeks ago with 5+ active contributors, while smartcropper last saw a commit 1 month ago with 11+ active contributors. 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.
halo-dev/halo
Mixed signals — read the receipts
copyleft license (GPL-3.0) — review compatibility; dependency CVE scan unavailable
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; dependency CVE scan unavailable
- ⚠Concentrated ownership — top contributor handles 60% of recent commits
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ✓Last commit today
- ✓5 active contributors
- ✓GPL-3.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
pqpo/smartcropper
Mixed signals — read the receipts
no tests detected in the complete Git tree; no CI workflows detected…
no tests detected in the complete Git tree; no CI workflows detected…
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; no CI workflows detected…
- ⚠Concentrated ownership — top contributor handles 64% of recent commits
- ⚠No CI workflows detected
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 4w ago
- ✓11 active contributors
What would improve this?
- •Use as dependency Mixed to Healthy if: add a test suite
- •Deploy as-is Mixed to 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
| halo | smartcropper | |
|---|---|---|
| Stars | 39,649 | 4,132 |
| Last commit | 15d ago | 1mo ago |
| License | GPL-3.0 | Unknown |
| Open issues | 116 | 38 |
| Has tests | ✓ | No |
| Has CI | ✓ | No |
| Test coverage | 31% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | C |
| Cycles | 0 | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? halo-dev/halo · pqpo/smartcropper
Ask AI about halo-dev/halo vs pqpo/smartcropper
Open the chat with a comparison question pre-filled.