How Supabase MCP scored a B.

• code

  68/100
  • ✓ Contributors & bus-factor: 18 recent contributors
  • ✓ Commit recency: last commit 1d ago
  • ✓ Commit cadence: 67 commits in 90 days
  • ✓ Issue close ratio: 51% of issues closed
  • ✓ Release cadence: 26 releases in 12 months
  • ✓ Stars (log-damped): 2,969 stars (log-damped)
  • – Star authenticity: star-velocity check unavailable — GitHub no longer publishes stargazer timestamps for this repo
  • ↓ Dependent repos: no public repos depend on it yet

• identity

  80/100
  • ✓ Organisation: Built by Supabase · notable organization (verified: Org profile shows a Verified badge stating the organization supabase controls the domains supabase.com and supabase.io; profile website https://supabase.com, description "The Postgres Development Platform.", location United States of America.)

• audits

  Not measured
  • – Third-party scans: no third-party scan data from listed registries

• freshness

  100/100
  • ✓ Last shipped: last commit 1d ago — standard-churn tools are expected to ship about every 120d
  • ✓ Registry listing: still listed on a registry 1d ago

• community

  68/100
  • – Recommends: no recommends from gate-passing builders yet
  • ✓ Hacker News mentions: 7 Hacker News stories pointing at this tool

Community did not lower this score. Community can only ever add. It did not raise the average for Supabase MCP, so the score shown is the one it would have without it. The component is still listed above, with its real value.

Components that could not be measured are left out of the average entirely, and their weight is redistributed, never scored as zero. Identity and Community are left out the same way when they would not have raised the score. How scores are calculated.