expressjs/express vs sindresorhus/slugify
expressjs/express shows stronger signals overall
As of September 2026, express shows healthier maintenance signals than slugify. express rates Healthy overall while slugify rates Mixed. express was committed to 4 days ago with 36+ active contributors, while slugify was committed to 3 days ago with 20+ 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.
expressjs/express
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.
- ✓In RepoPilot's curated trusted-corpus (29 projects)
- ✓Last commit 2d ago
- ✓36+ active contributors
- ✓Distributed ownership (top contributor 43% of recent commits)
- ✓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
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
| express | slugify | |
|---|---|---|
| Stars | 69,445 | 2,703 |
| Last commit | 4d ago | 3d ago |
| License | MIT | MIT |
| Open issues | 229 | 2 |
| Has tests | ✓ | No |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | A | — |
| Cycles | 0 | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? expressjs/express · sindresorhus/slugify
Ask AI about expressjs/express vs sindresorhus/slugify
Open the chat with a comparison question pre-filled.