sxei/chrome-plugin-demo vs trekhleb/javascript-algorithms
trekhleb/javascript-algorithms shows stronger signals overall
As of June 2026, javascript-algorithms shows healthier maintenance signals than chrome-plugin-demo. javascript-algorithms rates Healthy overall while chrome-plugin-demo rates Concerns. chrome-plugin-demo last saw a commit 3 years ago with 3+ active contributors, while javascript-algorithms was committed to 1 day ago with 34+ active contributors. 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.
sxei/chrome-plugin-demo →
Stale and unlicensed — last commit 3y ago
no license — legally unclear; last commit was 3y ago…
no license — can't legally use code; no tests detected…
Documented and popular — useful reference codebase to read through.
no license — can't legally use code; last commit was 3y ago…
- ⚠Stale — last commit 3y ago
- ⚠Small team — 3 contributors active in recent commits
- ⚠Concentrated ownership — top contributor handles 67% of recent commits
- ⚠No license — legally unclear to depend on
- ⚠No CI workflows detected
- ⚠No test directory detected
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓3 active contributors
What would improve this?
- →Use as dependency Concerns → Mixed if: publish a permissive license (MIT, Apache-2.0, etc.)
- →Fork & modify Concerns → Mixed if: add a LICENSE file
- →Deploy as-is Concerns → Mixed if: add a LICENSE file
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
trekhleb/javascript-algorithms →
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 57% of recent commits
- ✓Last commit today
- ✓34+ active contributors
- ✓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
| chrome-plugin-demo | javascript-algorithms | |
|---|---|---|
| Stars | 8,679 | 196,135 |
| Last commit | 3y ago | 1d ago |
| License | — | MIT |
| Open issues | 32 | 400 |
| Has tests | — | ✓ |
| Has CI | — | ✓ |
| Test coverage | 0% | 5% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | A |
| Cycles | — | 0 |
| Bottom-line | Concerns signals | Healthy signals |
Want the full analysis? sxei/chrome-plugin-demo · trekhleb/javascript-algorithms
Ask AI about sxei/chrome-plugin-demo vs trekhleb/javascript-algorithms
Open the chat with a comparison question pre-filled.