grasscutters/grasscutter vs proxyee-down-org/proxyee-down
Both showing Mixed signals — pick on fit, not health
As of September 2026, grasscutter and proxyee-down both show mixed maintenance signals. grasscutter last saw a commit 6 months ago with 23+ active contributors, while proxyee-down last saw a commit 2 years 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
Slowing — last commit 6mo ago
copyleft license (AGPL-3.0) — review compatibility; dependency CVE scan unavailable
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; dependency CVE scan unavailable
- ⚠Slowing — last commit 6mo ago
- ⚠AGPL-3.0 is copyleft — check downstream compatibility
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 6mo ago
- ✓23+ active contributors
- ✓Distributed ownership (top contributor 30% of recent commits)
- ✓AGPL-3.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Use as dependency Concerns to 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, cross-checked against OpenSSF Scorecard
proxyee-down-org/proxyee-down
Stale — last commit 2y ago
last commit was 2y ago; top contributor handles 93% of recent commits…
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; CI evidence incomplete…
- ⚠Stale — last commit 2y ago
- ⚠Single-maintainer risk — top contributor 93% of recent commits
- ✓7 active contributors
- ✓Apache-2.0 licensed
What would improve this?
- •Use as dependency Concerns to Mixed if: 1 commit in the last 365 days
- •Deploy as-is Mixed to 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,804 | 24,751 |
| Last commit | 6mo ago | 2y ago |
| License | AGPL-3.0 | Apache-2.0 |
| Open issues | 152 | 214 |
| Has tests | ✓ | Unknown |
| Has CI | ✓ | Unknown |
| Test coverage | 0% | 0% |
| Dependency CVEs | No CVEs | 0 critical · 0 high · 1 moderate · 0 low |
| Architecture grade | C | — |
| Cycles | 0 | — |
| 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.