RepoPilot

glanceapp/glance vs usefathom/fathom

Both showing Mixed signals — pick on fit, not health

As of September 2026, glance and fathom both show mixed maintenance signals. glance was committed to 1 week ago with 17+ active contributors, while fathom last saw a commit 6 months ago with 15+ active contributors. glance is AGPL-3.0-licensed while fathom 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.

glanceapp/glance

Mixed

Mixed signals — read the receipts

ConcernsDependency

copyleft license (AGPL-3.0) — review compatibility

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 73% of recent commits
  • AGPL-3.0 is copyleft — check downstream compatibility
  • Scorecard: default branch unprotected (0/10)
  • 1 moderate-severity advisory on direct dependencies
  • Last commit 2d ago
  • 17 active contributors
  • AGPL-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, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

usefathom/fathom

Mixed

Slowing — last commit 6mo ago

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.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10

  • Slowing — last commit 6mo ago
  • Scorecard: marked unmaintained (0/10)
  • Scorecard: default branch unprotected (0/10)
  • Last commit 6mo ago
  • 15 active contributors
  • Distributed ownership (top contributor 49% of recent commits)
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • 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 dependency CVEs from deps.dev and OpenSSF Scorecard

Signal-by-signal breakdown

glancefathom
Stars36,8958,018
Last commit11d ago6mo ago
LicenseAGPL-3.0MIT
Open issues3155
Has tests
Has CI
Test coverage5%20%
Dependency CVEs0 critical · 0 high · 1 moderate · 0 lowNo CVEs
Architecture gradeAA
Cycles00
Bottom-lineMixed signalsMixed signals

Want the full analysis? glanceapp/glance · usefathom/fathom

Ask AI about glanceapp/glance vs usefathom/fathom

Open the chat with a comparison question pre-filled.