RepoPilot

fatedier/frp vs go-gitea/gitea

Both showing Healthy signals — pick on fit, not health

As of September 2026, frp and gitea both show healthy maintenance signals. frp was committed to 2 weeks ago with 11+ active contributors, while gitea was committed to 2 weeks ago with 29+ active contributors. frp is Apache-2.0-licensed while gitea is MIT-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.

fatedier/frp

Healthy

Healthy across all four use cases

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

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

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No blocking repository-level signals were found; deployment review is still required.

  • Single-maintainer risk — top contributor 88% of recent commits
  • Last commit 1d ago
  • 11 active contributors
  • Apache-2.0 licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

go-gitea/gitea

Healthy

Healthy across all four use cases

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

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

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No blocking repository-level signals were found; deployment review is still required.

  • Scorecard: dangerous CI workflow (0/10)
  • Last commit today
  • 29+ active contributors
  • Distributed ownership (top contributor 27% of recent commits)
  • MIT licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

Signal-by-signal breakdown

frpgitea
Stars109,09157,721
Last commit18d ago16d ago
LicenseApache-2.0MIT
Open issues492,522
Has tests
Has CI
Test coverage59%90%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? fatedier/frp · go-gitea/gitea

Ask AI about fatedier/frp vs go-gitea/gitea

Open the chat with a comparison question pre-filled.