mouredev/hello-java vs proxyee-down-org/proxyee-down
Both showing Mixed signals — pick on fit, not health
As of June 2026, hello-java and proxyee-down both show mixed maintenance signals. hello-java last saw a commit 11 months ago with 1+ active contributor, while proxyee-down last saw a commit 1 year ago with 7+ active contributors. Both use the Apache-2.0 license. 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.
mouredev/hello-java →
Slowing — last commit 10mo ago
single-maintainer (no co-maintainers visible); no tests detected…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 10mo ago; Scorecard "Branch-Protection" is 0/10…
- ⚠Slowing — last commit 10mo ago
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠No CI workflows detected
- ⚠No test directory detected
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 10mo ago
- ✓Apache-2.0 licensed
What would improve this?
- →Use as dependency Mixed → Healthy if: onboard a second core maintainer; add a test suite
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days; bring "Branch-Protection" to ≥3/10 (see scorecard report)
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…
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
| hello-java | proxyee-down | |
|---|---|---|
| Stars | 4,158 | 24,751 |
| Last commit | 11mo ago | 1y ago |
| License | Apache-2.0 | Apache-2.0 |
| Open issues | 3 | 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? mouredev/hello-java · proxyee-down-org/proxyee-down
Ask AI about mouredev/hello-java vs proxyee-down-org/proxyee-down
Open the chat with a comparison question pre-filled.