hapijs/hapi vs sindresorhus/slugify
Both showing Mixed signals — pick on fit, not health
As of September 2026, hapi and slugify both show mixed maintenance signals. hapi last saw a commit 1 month ago with 21+ active contributors, while slugify was committed to 1 week ago with 20+ active contributors. 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.
hapijs/hapi
Evidence incomplete — review before adopting
license evidence incomplete
license evidence incomplete
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)
- ⚠Could not verify license from the available repository evidence
- ✓Last commit 4w ago
- ✓21+ active contributors
- ✓Distributed ownership (top contributor 35% of recent commits)
- ✓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
sindresorhus/slugify
Mixed signals — read the receipts
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
- ⚠Concentrated ownership — top contributor handles 70% of recent commits
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 3d ago
- ✓20 active contributors
- ✓MIT licensed
- ✓CI configured
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
Signal-by-signal breakdown
| hapi | slugify | |
|---|---|---|
| Stars | 14,792 | 2,703 |
| Last commit | 1mo ago | 7d ago |
| License | Unknown | MIT |
| Open issues | 56 | 2 |
| Has tests | ✓ | No |
| Has CI | ✓ | ✓ |
| Test coverage | 71% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? hapijs/hapi · sindresorhus/slugify
Ask AI about hapijs/hapi vs sindresorhus/slugify
Open the chat with a comparison question pre-filled.