sveltejs/svelte vs sxei/chrome-plugin-demo
sveltejs/svelte shows stronger signals overall
As of June 2026, svelte shows healthier maintenance signals than chrome-plugin-demo. svelte rates Healthy overall while chrome-plugin-demo rates Concerns. svelte was committed to today with 25+ active contributors, while chrome-plugin-demo last saw a commit 3 years ago with 3+ 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.
sveltejs/svelte →
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.
- ⚠Scorecard: dangerous CI workflow (0/10)
- ✓In RepoPilot's curated trusted-corpus (29 projects)
- ✓Last commit today
- ✓25+ active contributors
- ✓Distributed ownership (top contributor 34% 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
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
Signal-by-signal breakdown
| svelte | chrome-plugin-demo | |
|---|---|---|
| Stars | 87,436 | 8,679 |
| Last commit | today | 3y ago |
| License | MIT | — |
| Open issues | 1,051 | 32 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 4% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Concerns signals |
Want the full analysis? sveltejs/svelte · sxei/chrome-plugin-demo
Ask AI about sveltejs/svelte vs sxei/chrome-plugin-demo
Open the chat with a comparison question pre-filled.