ds300/patch-package vs nilbuild/developer-roadmap
Both showing Mixed signals — pick on fit, not health
As of June 2026, patch-package and developer-roadmap both show mixed maintenance signals. patch-package last saw a commit 8 months ago with 10+ active contributors, while developer-roadmap was committed to 2 days ago with 17+ active contributors. patch-package is MIT-licensed while developer-roadmap is Other-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.
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)
Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests + OpenSSF Scorecard
nilbuild/developer-roadmap →
Mixed signals — read the receipts
non-standard license (Other); no tests detected
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; 8 cyclic import chains — pervasive coupling
- ⚠Concentrated ownership — top contributor handles 73% of recent commits
- ⚠Non-standard license (Other) — review terms
- ⚠No test directory detected
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 2d ago
- ✓17 active contributors
- ✓Other licensed
- ✓CI configured
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
- →Deploy as-is Mixed → Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)
Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests + OpenSSF Scorecard
Signal-by-signal breakdown
| patch-package | developer-roadmap | |
|---|---|---|
| Stars | 11,177 | 357,584 |
| Last commit | 8mo ago | 2d ago |
| License | MIT | Other |
| Open issues | 278 | 18 |
| Has tests | ✓ | — |
| Has CI | ✓ | ✓ |
| Test coverage | 1% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | C |
| Cycles | — | 8 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? ds300/patch-package · nilbuild/developer-roadmap
Ask AI about ds300/patch-package vs nilbuild/developer-roadmap
Open the chat with a comparison question pre-filled.