dotnetcore/util vs peass-ng/peass-ng
Both showing Mixed signals — pick on fit, not health
As of June 2026, util and peass-ng both show mixed maintenance signals. util last saw a commit 1 year ago with 3+ active contributors, while peass-ng last saw a commit 1 month ago with 9+ active contributors. util is MIT-licensed while peass-ng 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.
dotnetcore/util →
Stale — last commit 2y ago
last commit was 2y ago; top contributor handles 98% of recent commits…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; no CI workflows detected
- ⚠Stale — last commit 2y ago
- ⚠Small team — 3 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 98% of recent commits
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓3 active contributors
- ✓MIT licensed
What would improve this?
- →Use as dependency Concerns → Mixed if: 1 commit in the last 365 days
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
peass-ng/peass-ng →
Single-maintainer risk — review before adopting
non-standard license (Other)
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.
- ⚠Single-maintainer risk — top contributor 80% of recent commits
- ⚠Non-standard license (Other) — review terms
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 4d ago
- ✓9 active contributors
- ✓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, cross-checked against OpenSSF Scorecard
Signal-by-signal breakdown
| util | peass-ng | |
|---|---|---|
| Stars | 4,618 | 19,838 |
| Last commit | 1y ago | 1mo ago |
| License | MIT | Other |
| Open issues | 3 | 1 |
| Has tests | — | ✓ |
| Has CI | — | ✓ |
| Test coverage | 0% | 8% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? dotnetcore/util · peass-ng/peass-ng
Ask AI about dotnetcore/util vs peass-ng/peass-ng
Open the chat with a comparison question pre-filled.