railwayapp/nixpacks vs starship/starship
Both showing Healthy signals — pick on fit, not health
As of September 2026, nixpacks and starship both show healthy maintenance signals. nixpacks was committed to 4 weeks ago with 31+ active contributors, while starship was committed to 1 week ago with 15+ active contributors. nixpacks is MIT-licensed while starship is ISC-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.
railwayapp/nixpacks
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; 6 cyclic import chains — pervasive coupling
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓31+ active contributors
- ✓Distributed ownership (top contributor 38% 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
starship/starship
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 "Token-Permissions" is 0/10; 8 cyclic import chains — pervasive coupling
- ⚠Concentrated ownership — top contributor handles 77% of recent commits
- ✓Last commit today
- ✓15 active contributors
- ✓ISC licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: bring "Token-Permissions" 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
| nixpacks | starship | |
|---|---|---|
| Stars | 3,548 | 59,805 |
| Last commit | 29d ago | 8d ago |
| License | MIT | ISC |
| Open issues | 98 | 1,046 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 46% | 2% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | C |
| Cycles | 6 | 8 |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? railwayapp/nixpacks · starship/starship
Ask AI about railwayapp/nixpacks vs starship/starship
Open the chat with a comparison question pre-filled.