How JSON Render scored a B.

• code

  60/100
  • ✓ Contributors & bus-factor: 16 recent contributors
  • ✓ Commit recency: last commit 9d ago
  • ✓ Commit cadence: 15 commits in 90 days
  • ✓ Issue close ratio: 46% of issues closed
  • ✓ Release cadence: 100 releases in 12 months
  • ✓ Stars (log-damped): 18,759 stars (log-damped)
  • ↓ Star authenticity: engagement of 0.08 per star — star signal discounted by 21%
  • ↓ Dependent repos: no public repos depend on it yet

• identity

  80/100
  • ✓ Organisation: Built by Vercel · notable organization (verified: Org profile shows a Verified badge stating the organization vercel controls the domain vercel.com; profile website https://vercel.com, description "Agentic infrastructure for every app and agent.". The mapped org vercel-labs also shows a Verified badge for vercel.com.)

• audits

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

• freshness

  100/100
  • ✓ Last shipped: last release 9d ago — fast-churn frameworks are expected to ship about every 60d
  • ✓ Registry listing: still listed on a registry 0d ago

• community

  46/100
  • – Recommends: no recommends from gate-passing builders yet
  • ✓ Hacker News mentions: 3 Hacker News stories pointing at this tool
  • – Signal depth: sparse data — this is an early reading from very few data points

Community did not lower this score. Community can only ever add. It did not raise the average for JSON Render, 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.