spf13/cobra vs teh-cmc/go-internals
spf13/cobra shows stronger signals overall
As of June 2026, cobra shows healthier maintenance signals than go-internals. cobra rates Healthy overall while go-internals rates Mixed. cobra last saw a commit 2 months ago with 51+ active contributors, while go-internals last saw a commit 5 years ago with 4+ active contributors. cobra is Apache-2.0-licensed while go-internals 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.
spf13/cobra →
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 2w ago
- ✓51+ active contributors
- ✓Distributed ownership (top contributor 11% of recent commits)
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
teh-cmc/go-internals →
Stale — last commit 5y ago
non-standard license (Other); last commit was 5y ago…
no tests detected; no CI workflows detected…
Documented and popular — useful reference codebase to read through.
last commit was 5y ago; Scorecard "Branch-Protection" is 0/10…
- ⚠Stale — last commit 5y ago
- ⚠Small team — 4 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 83% of recent commits
- ⚠Non-standard license (Other) — review terms
- ⚠No CI workflows detected
- ⚠No test directory detected
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓4 active contributors
- ✓Other licensed
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
- →Fork & modify Mixed → Healthy if: 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
Signal-by-signal breakdown
| cobra | go-internals | |
|---|---|---|
| Stars | 43,893 | 7,934 |
| Last commit | 2mo ago | 5y ago |
| License | Apache-2.0 | Other |
| Open issues | 363 | 11 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 3% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? spf13/cobra · teh-cmc/go-internals
Ask AI about spf13/cobra vs teh-cmc/go-internals
Open the chat with a comparison question pre-filled.