azure/dotnetty vs dnspy/dnspy
azure/dotnetty shows stronger signals overall
As of June 2026, dotnetty shows stronger maintenance signals than dnspy. dotnetty rates Mixed overall while dnspy rates Concerns. dotnetty last saw a commit 5 months ago with 30+ active contributors, while dnspy last saw a commit 5 years ago with 7+ 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.
azure/dotnetty →
Slowing — last commit 4mo ago
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.
No critical CVEs, sane security posture — runnable as-is.
- ⚠Slowing — last commit 4mo ago
- ⚠Non-standard license (Other) — review terms
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓Last commit 4mo ago
- ✓30+ active contributors
- ✓Distributed ownership (top contributor 19% of recent commits)
- ✓Other licensed
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
dnspy/dnspy →
Stale and unlicensed — last commit 5y ago
no license — legally unclear; last commit was 5y 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 5y ago
- ⚠Stale — last commit 5y ago
- ⚠Single-maintainer risk — top contributor 91% of recent commits
- ⚠No license — legally unclear to depend on
- ⚠No test directory detected
- ✓7 active contributors
- ✓CI configured
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
Signal-by-signal breakdown
| dotnetty | dnspy | |
|---|---|---|
| Stars | 4,236 | 29,364 |
| Last commit | 5mo ago | 5y ago |
| License | Other | — |
| Open issues | 174 | 185 |
| Has tests | — | — |
| Has CI | — | ✓ |
| Test coverage | 0% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Concerns signals |
Want the full analysis? azure/dotnetty · dnspy/dnspy
Ask AI about azure/dotnetty vs dnspy/dnspy
Open the chat with a comparison question pre-filled.