keystonejs/keystone vs tryghost/ghost
tryghost/ghost shows stronger signals overall
As of September 2026, ghost shows healthier maintenance signals than keystone. ghost rates Healthy overall while keystone rates Mixed. keystone was committed to 3 weeks ago with 6+ active contributors, while ghost was committed to 4 days ago with 11+ 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.
keystonejs/keystone
Single-maintainer risk — review before adopting
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 1/10; Scorecard "Token-Permissions" is 0/10
- ⚠Single-maintainer risk — top contributor 87% of recent commits
- ⚠Scorecard: default branch unprotected (1/10)
- ✓Last commit today
- ✓6 active contributors
- ✓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
tryghost/ghost
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.
- ✓Last commit today
- ✓11 active contributors
- ✓Distributed ownership (top contributor 34% 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
Signal-by-signal breakdown
| keystone | ghost | |
|---|---|---|
| Stars | 9,963 | 55,292 |
| Last commit | 24d ago | 4d ago |
| License | MIT | MIT |
| Open issues | 144 | 189 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 33% | 59% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? keystonejs/keystone · tryghost/ghost
Ask AI about keystonejs/keystone vs tryghost/ghost
Open the chat with a comparison question pre-filled.