spf13/viper vs urfave/cli
urfave/cli shows stronger signals overall
As of September 2026, cli shows healthier maintenance signals than viper. cli rates Healthy overall while viper rates Mixed. viper last saw a commit 8 months ago with 11+ active contributors, while cli was committed to 2 days ago with 19+ 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.
spf13/viper
Slowing — last commit 8mo ago
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
last commit was 8mo ago; Scorecard "Token-Permissions" is 0/10
- ⚠Slowing — last commit 8mo ago
- ⚠Scorecard: marked unmaintained (0/10)
- ✓Last commit 8mo ago
- ✓11 active contributors
- ✓Distributed ownership (top contributor 36% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
urfave/cli
Healthy across all four use cases
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
No blocking repository-level signals were found; deployment review is still required.
- ⚠Concentrated ownership — top contributor handles 52% of recent commits
- ✓Last commit 1d ago
- ✓19 active contributors
- ✓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
| viper | cli | |
|---|---|---|
| Stars | 30,458 | 24,235 |
| Last commit | 8mo ago | 2d ago |
| License | MIT | MIT |
| Open issues | 133 | 69 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 57% | 63% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? spf13/viper · urfave/cli
Ask AI about spf13/viper vs urfave/cli
Open the chat with a comparison question pre-filled.