RepoPilot

proxyee-down-org/proxyee-down vs threekiii/awesome-poc

Both showing Mixed signals — pick on fit, not health

As of September 2026, proxyee-down and awesome-poc both show mixed maintenance signals. proxyee-down last saw a commit 2 years ago with 7+ active contributors, while awesome-poc last saw a commit 4 months ago with 1+ active contributor. 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.

proxyee-down-org/proxyee-down

Mixed

Stale — last commit 2y ago

ConcernsDependency

last commit was 2y ago; top contributor handles 93% of recent commits…

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

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

threekiii/awesome-poc

Mixed

Slowing — last commit 4mo ago

MixedDependency

single-maintainer (no co-maintainers visible); no tests detected in the complete Git tree…

MixedFork & modify

no tests detected in the complete Git tree; no CI workflows detected…

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; no CI workflows detected…

  • Slowing — last commit 4mo ago
  • Solo or near-solo (1 contributor active in recent commits)
  • No CI workflows detected
  • No tests detected in the complete Git tree
  • Scorecard: default branch unprotected (0/10)
  • Last commit 4mo ago

What would improve this?

  • Use as dependency Mixed to Healthy if: onboard a second core maintainer; add a test suite
  • Deploy as-is Mixed to Healthy if: 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

Signal-by-signal breakdown

proxyee-downawesome-poc
Stars24,7515,191
Last commit2y ago4mo ago
LicenseApache-2.0Unknown
Open issues2142
Has testsUnknownNo
Has CIUnknownNo
Test coverage0%0%
Dependency CVEs0 critical · 0 high · 1 moderate · 0 lowNo CVEs
Architecture gradeC
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? proxyee-down-org/proxyee-down · threekiii/awesome-poc

Ask AI about proxyee-down-org/proxyee-down vs threekiii/awesome-poc

Open the chat with a comparison question pre-filled.