halo-dev/halo vs threekiii/awesome-poc
Both showing Mixed signals — pick on fit, not health
As of September 2026, halo and awesome-poc both show mixed maintenance signals. halo was committed to 2 weeks ago with 5+ active contributors, while awesome-poc last saw a commit 4 months ago with 1+ active contributor. 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
threekiii/awesome-poc
Slowing — last commit 4mo ago
single-maintainer (no co-maintainers visible); no tests detected in the complete Git tree…
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…
- ⚠Slowing — last commit 4mo ago
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠No CI workflows detected
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 4mo ago
What would improve this?
- •Use as dependency Mixed to Healthy if: onboard a second core maintainer; 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 | awesome-poc | |
|---|---|---|
| Stars | 39,649 | 5,191 |
| Last commit | 15d ago | 4mo ago |
| License | GPL-3.0 | Unknown |
| Open issues | 116 | 2 |
| 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 · threekiii/awesome-poc
Ask AI about halo-dev/halo vs threekiii/awesome-poc
Open the chat with a comparison question pre-filled.