alecthomas/kong vs spf13/viper
alecthomas/kong shows stronger signals overall
As of September 2026, kong shows healthier maintenance signals than viper. kong rates Healthy overall while viper rates Mixed. kong was committed to 1 week ago with 33+ active contributors, while viper last saw a commit 8 months ago with 11+ 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.
alecthomas/kong
Strong maintenance signals
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.
Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 6d ago
- ✓33+ active contributors
- ✓Distributed ownership (top contributor 27% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓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 dependency CVEs from deps.dev and OpenSSF Scorecard
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
Signal-by-signal breakdown
| kong | viper | |
|---|---|---|
| Stars | 3,172 | 30,458 |
| Last commit | 8d ago | 8mo ago |
| License | MIT | MIT |
| Open issues | 44 | 133 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 59% | 57% |
| Dependency CVEs | 0 critical · 0 high · 1 moderate · 0 low | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? alecthomas/kong · spf13/viper
Ask AI about alecthomas/kong vs spf13/viper
Open the chat with a comparison question pre-filled.