shadowsocksr-backup/shadowsocksr-csharp vs thangchung/awesome-dotnet-core
Both showing Mixed signals — pick on fit, not health
As of June 2026, shadowsocksr-csharp and awesome-dotnet-core both show mixed maintenance signals. shadowsocksr-csharp last saw a commit 7 years ago with 2+ active contributors, while awesome-dotnet-core last saw a commit 4 months ago with 34+ 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.
shadowsocksr-backup/shadowsocksr-csharp →
Stale — last commit 7y ago
copyleft license (GPL-3.0) — review compatibility; last commit was 7y ago…
no CI workflows detected; no description (proxy for README missing)…
no description (proxy for README missing); last commit was 7y ago
last commit was 7y ago; no CI workflows detected
- ⚠Stale — last commit 7y ago
- ⚠Small team — 2 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 99% of recent commits
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠No CI workflows detected
- ✓2 active contributors
- ✓GPL-3.0 licensed
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
- →Fork & modify Mixed → Healthy if: wire up GitHub Actions or equivalent
- →Learn from Mixed → Healthy if: add a README + repo description
- →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
thangchung/awesome-dotnet-core →
Missing license — unclear to depend on
no license — legally unclear; no tests detected
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
- ⚠No license — legally unclear to depend on
- ⚠No test directory detected
- ✓Last commit 2mo ago
- ✓34+ active contributors
- ✓Distributed ownership (top contributor 42% of recent commits)
- ✓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
| shadowsocksr-csharp | awesome-dotnet-core | |
|---|---|---|
| Stars | 4,511 | 21,225 |
| Last commit | 7y ago | 4mo ago |
| License | GPL-3.0 | — |
| Open issues | 10 | 193 |
| Has tests | ✓ | — |
| Has CI | — | ✓ |
| Test coverage | 4% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? shadowsocksr-backup/shadowsocksr-csharp · thangchung/awesome-dotnet-core
Ask AI about shadowsocksr-backup/shadowsocksr-csharp vs thangchung/awesome-dotnet-core
Open the chat with a comparison question pre-filled.