forem/forem vs galetahub/ckeditor
Both showing Mixed signals — pick on fit, not health
As of September 2026, forem and ckeditor both show mixed maintenance signals. forem was committed to 1 day ago with 13+ active contributors, while ckeditor last saw a commit 1 year ago with 18+ active contributors. forem is AGPL-3.0-licensed while ckeditor 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.
forem/forem
Mixed signals — read the receipts
copyleft license (AGPL-3.0) — review compatibility; dependency CVE scan unavailable
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; dependency CVE scan unavailable
- ⚠Concentrated ownership — top contributor handles 53% of recent commits
- ⚠AGPL-3.0 is copyleft — check downstream compatibility
- ✓Last commit today
- ✓13 active contributors
- ✓AGPL-3.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
galetahub/ckeditor
Stale — last commit 2y ago
last commit was 2y ago; no CI workflows detected…
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; Scorecard "Branch-Protection" is 0/10…
- ⚠Stale — last commit 2y ago
- ⚠Concentrated ownership — top contributor handles 69% of recent commits
- ⚠No CI workflows detected
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓18 active contributors
- ✓MIT licensed
- ✓Tests present
What would improve this?
- •Use as dependency Mixed to Healthy if: 1 commit in the last 365 days
- •Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days; 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 OpenSSF Scorecard
Signal-by-signal breakdown
| forem | ckeditor | |
|---|---|---|
| Stars | 22,777 | 2,224 |
| Last commit | 1d ago | 1y ago |
| License | AGPL-3.0 | MIT |
| Open issues | 134 | 16 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | No |
| Test coverage | 64% | 80% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | C |
| Cycles | — | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? forem/forem · galetahub/ckeditor
Ask AI about forem/forem vs galetahub/ckeditor
Open the chat with a comparison question pre-filled.