n8n-io/n8n vs nhn/tui.calendar
n8n-io/n8n shows stronger signals overall
As of June 2026, n8n shows healthier maintenance signals than tui.calendar. n8n rates Healthy overall while tui.calendar rates Mixed. n8n was committed to today with 42+ active contributors, while tui.calendar last saw a commit 2 years ago with 7+ active contributors. n8n is Other-licensed while tui.calendar 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.
n8n-io/n8n →
Healthy across the board
non-standard license (Other)
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
No critical CVEs, sane security posture — runnable as-is.
- ⚠Non-standard license (Other) — review terms
- ✓Last commit today
- ✓42+ active contributors
- ✓Distributed ownership (top contributor 13% of recent commits)
- ✓Other licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
nhn/tui.calendar →
Stale — last commit 2y ago
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
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
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓7 active contributors
- ✓Distributed ownership (top contributor 43% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Deploy as-is Mixed → 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
| n8n | tui.calendar | |
|---|---|---|
| Stars | 194,262 | 12,639 |
| Last commit | today | 2y ago |
| License | Other | MIT |
| Open issues | 1,482 | 208 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 2% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? n8n-io/n8n · nhn/tui.calendar
Ask AI about n8n-io/n8n vs nhn/tui.calendar
Open the chat with a comparison question pre-filled.