bevyengine/bevy vs railwayapp/nixpacks
Both showing Healthy signals — pick on fit, not health
As of September 2026, bevy and nixpacks both show healthy maintenance signals. bevy was committed to 3 weeks ago with 57+ active contributors, while nixpacks last saw a commit 1 month ago with 31+ active contributors. bevy is Apache-2.0-licensed while nixpacks is MIT-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.
bevyengine/bevy
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.
- ⚠Scorecard: dangerous CI workflow (0/10)
- ✓Last commit today
- ✓57+ active contributors
- ✓Distributed ownership (top contributor 10% of recent commits)
- ✓Apache-2.0 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
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
Signal-by-signal breakdown
| bevy | nixpacks | |
|---|---|---|
| Stars | 47,810 | 3,548 |
| Last commit | 24d ago | 1mo ago |
| License | Apache-2.0 | MIT |
| Open issues | 3,424 | 98 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 8% | 46% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | C |
| Cycles | — | 6 |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? bevyengine/bevy · railwayapp/nixpacks
Ask AI about bevyengine/bevy vs railwayapp/nixpacks
Open the chat with a comparison question pre-filled.