grasscutters/grasscutter vs proxyee-down-org/proxyee-down
Both showing Mixed signals — pick on fit, not health
As of June 2026, grasscutter and proxyee-down both show mixed maintenance signals. grasscutter last saw a commit 3 months ago with 23+ active contributors, while proxyee-down last saw a commit 1 year ago with 7+ active contributors. grasscutter is AGPL-3.0-licensed while proxyee-down is Apache-2.0-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.
grasscutters/grasscutter →
Mixed signals — read the receipts
copyleft license (AGPL-3.0) — review compatibility; 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.
- ⚠AGPL-3.0 is copyleft — check downstream compatibility
- ⚠No test directory detected
- ✓Last commit 2mo ago
- ✓23+ active contributors
- ✓Distributed ownership (top contributor 30% of recent commits)
- ✓AGPL-3.0 licensed
- ✓CI configured
What would improve this?
- →Use as dependency Concerns → Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
proxyee-down-org/proxyee-down →
Stale — last commit 2y ago
last commit was 2y ago; top contributor handles 93% 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
- ⚠Single-maintainer risk — top contributor 93% of recent commits
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓7 active contributors
- ✓Apache-2.0 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
Signal-by-signal breakdown
| grasscutter | proxyee-down | |
|---|---|---|
| Stars | 16,753 | 24,751 |
| Last commit | 3mo ago | 1y ago |
| License | AGPL-3.0 | Apache-2.0 |
| Open issues | 150 | 214 |
| Has tests | — | — |
| Has CI | ✓ | — |
| Test coverage | 0% | 0% |
| Dependency CVEs | No CVEs | 0 critical · 0 high · 1 moderate · 0 low |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? grasscutters/grasscutter · proxyee-down-org/proxyee-down
Ask AI about grasscutters/grasscutter vs proxyee-down-org/proxyee-down
Open the chat with a comparison question pre-filled.