ds300/patch-package vs solidjs/solid
solidjs/solid shows stronger signals overall
As of June 2026, solid shows healthier maintenance signals than patch-package. solid rates Healthy overall while patch-package rates Mixed. patch-package last saw a commit 9 months ago with 10+ active contributors, while solid was committed to today with 27+ 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.
ds300/patch-package →
Slowing — last commit 8mo 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 8mo ago; Scorecard "Branch-Protection" is 0/10…
- ⚠Slowing — last commit 8mo ago
- ⚠Concentrated ownership — top contributor handles 64% of recent commits
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 8mo ago
- ✓10 active contributors
- ✓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
solidjs/solid →
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.
Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10
- ⚠Concentrated ownership — top contributor handles 63% of recent commits
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓27+ active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Deploy as-is Mixed → Healthy if: 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 dependency CVEs from deps.dev and OpenSSF Scorecard
Signal-by-signal breakdown
| patch-package | solid | |
|---|---|---|
| Stars | 11,177 | 35,660 |
| Last commit | 9mo ago | today |
| License | MIT | MIT |
| Open issues | 278 | 59 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 1% | 75% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? ds300/patch-package · solidjs/solid
Ask AI about ds300/patch-package vs solidjs/solid
Open the chat with a comparison question pre-filled.