RepoPilot

bevyengine/bevy vs schniz/fnm

Both showing Healthy signals — pick on fit, not health

As of September 2026, bevy and fnm both show healthy maintenance signals. bevy was committed to 3 weeks ago with 57+ active contributors, while fnm last saw a commit 4 months ago with 23+ active contributors. bevy is Apache-2.0-licensed while fnm is GPL-3.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.

bevyengine/bevy

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
  • 57+ active contributors
  • Distributed ownership (top contributor 10% of recent commits)
  • 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

schniz/fnm

Healthy

Strong maintenance signals

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility; dependency CVE scan unavailable

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

dependency CVE scan unavailable

  • GPL-3.0 is copyleft — check downstream compatibility
  • Last commit 3w ago
  • 23+ active contributors
  • Distributed ownership (top contributor 49% of recent commits)
  • GPL-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

Signal-by-signal breakdown

bevyfnm
Stars47,81025,417
Last commit22d ago4mo ago
LicenseApache-2.0GPL-3.0
Open issues3,424214
Has tests
Has CI
Test coverage8%9%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? bevyengine/bevy · schniz/fnm

Ask AI about bevyengine/bevy vs schniz/fnm

Open the chat with a comparison question pre-filled.