microsoft/vscode vs nhn/tui.calendar
microsoft/vscode shows stronger signals overall
As of June 2026, vscode shows healthier maintenance signals than tui.calendar. vscode rates Healthy overall while tui.calendar rates Mixed. vscode was committed to today with 24+ active contributors, while tui.calendar last saw a commit 2 years ago with 7+ 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.
microsoft/vscode →
Healthy across the board
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.
No critical CVEs, sane security posture — runnable as-is.
- ✓In RepoPilot's curated trusted-corpus (29 projects)
- ✓Last commit today
- ✓24+ active contributors
- ✓Distributed ownership (top contributor 28% 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
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
| vscode | tui.calendar | |
|---|---|---|
| Stars | 186,836 | 12,639 |
| Last commit | today | 2y ago |
| License | MIT | MIT |
| Open issues | 18,813 | 208 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 4% | 2% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? microsoft/vscode · nhn/tui.calendar
Ask AI about microsoft/vscode vs nhn/tui.calendar
Open the chat with a comparison question pre-filled.