kodezi/chronos vs seleniumhq/selenium
seleniumhq/selenium shows stronger signals overall
As of June 2026, selenium shows healthier maintenance signals than chronos. selenium rates Healthy overall while chronos rates Mixed. chronos last saw a commit 7 months ago with 1+ active contributor, while selenium was committed to 3 weeks ago with 9+ active contributors. chronos is Other-licensed while selenium 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.
kodezi/chronos →
Slowing — last commit 6mo ago
non-standard license (Other); single-maintainer (no co-maintainers visible)
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.
- ⚠Slowing — last commit 6mo ago
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠Non-standard license (Other) — review terms
- ✓Last commit 6mo ago
- ✓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
seleniumhq/selenium →
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.
- ⚠Concentrated ownership — top contributor handles 66% of recent commits
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓9 active contributors
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
Signal-by-signal breakdown
| chronos | selenium | |
|---|---|---|
| Stars | 4,950 | 34,146 |
| Last commit | 7mo ago | 24d ago |
| License | Other | Apache-2.0 |
| Open issues | 0 | 186 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 6% | 2% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | C |
| Cycles | — | 0 |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? kodezi/chronos · seleniumhq/selenium
Ask AI about kodezi/chronos vs seleniumhq/selenium
Open the chat with a comparison question pre-filled.