helix-editor/helix vs trunk-rs/trunk
Both showing Healthy signals — pick on fit, not health
As of September 2026, helix and trunk both show healthy maintenance signals. helix was committed to 2 weeks ago with 48+ active contributors, while trunk was committed to 3 weeks ago with 21+ active contributors. helix is MPL-2.0-licensed while trunk is Apache-2.0-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.
helix-editor/helix
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: default branch unprotected (0/10)
- ✓Last commit 1d ago
- ✓48+ active contributors
- ✓Distributed ownership (top contributor 19% of recent commits)
- ✓MPL-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
trunk-rs/trunk
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; 8 cyclic import chains — pervasive coupling
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 2w ago
- ✓21+ active contributors
- ✓Distributed ownership (top contributor 36% of recent commits)
- ✓Apache-2.0 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
| helix | trunk | |
|---|---|---|
| Stars | 46,068 | 4,389 |
| Last commit | 15d ago | 21d ago |
| License | MPL-2.0 | Apache-2.0 |
| Open issues | 1,638 | 136 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 8% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | A | C |
| Cycles | 0 | 8 |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? helix-editor/helix · trunk-rs/trunk
Ask AI about helix-editor/helix vs trunk-rs/trunk
Open the chat with a comparison question pre-filled.