RepoPilot

fatedier/frp vs nats-io/nats-server

Both showing Healthy signals — pick on fit, not health

As of September 2026, frp and nats-server both show healthy maintenance signals. frp was committed to 2 weeks ago with 11+ active contributors, while nats-server was committed to 3 weeks 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.

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

nats-io/nats-server

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.

  • Concentrated ownership — top contributor handles 53% of recent commits
  • 1 moderate-severity advisory on direct dependencies
  • Last commit 1d ago
  • 7 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

Signal-by-signal breakdown

frpnats-server
Stars109,09120,564
Last commit15d ago22d ago
LicenseApache-2.0Apache-2.0
Open issues49544
Has tests
Has CI
Test coverage59%100%
Dependency CVEsNo CVEs0 critical · 0 high · 1 moderate · 0 low
Architecture grade
Cycles
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? fatedier/frp · nats-io/nats-server

Ask AI about fatedier/frp vs nats-io/nats-server

Open the chat with a comparison question pre-filled.