halo-dev/halo vs tencent/apijson
Both showing Mixed signals — pick on fit, not health
As of September 2026, halo and apijson both show mixed maintenance signals. halo was committed to 1 week ago with 5+ active contributors, while apijson was committed to 3 weeks ago with 8+ active contributors. halo is GPL-3.0-licensed while apijson is Apache-2.0-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.
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
tencent/apijson
Single-maintainer risk — review before adopting
no CI workflows detected; 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 "Branch-Protection" is 0/10; no CI workflows detected…
- ⚠Single-maintainer risk — top contributor 82% of recent commits
- ⚠No CI workflows detected
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 2d ago
- ✓8 active contributors
- ✓Apache-2.0 licensed
- ✓Tests present
What would improve this?
- •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 | apijson | |
|---|---|---|
| Stars | 39,649 | 18,399 |
| Last commit | 10d ago | 26d ago |
| License | GPL-3.0 | Apache-2.0 |
| Open issues | 116 | 241 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | No |
| Test coverage | 31% | 3% |
| 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 · tencent/apijson
Ask AI about halo-dev/halo vs tencent/apijson
Open the chat with a comparison question pre-filled.