How Typechat scored a B.

• code

  59/100
  • ✓ Contributors & bus-factor: 15 recent contributors
  • ✓ Commit recency: last commit 3d ago
  • ✓ Commit cadence: 27 commits in 90 days
  • ✓ Issue close ratio: 77% of issues closed
  • ↓ Release cadence: 0 releases in 12 months
  • ✓ Stars (log-damped): 8,692 stars (log-damped)
  • ↓ Star authenticity: engagement of 0.11 per star — star signal discounted by 7%
  • ✓ Dependent repos: 15 public repos depend on it

• identity

  80/100
  • ✓ Organisation: Built by Microsoft · notable organization (verified: Org profile shows a Verified badge for opensource.microsoft.com and microsoft.com; profile website https://opensource.microsoft.com, description "Open source projects and samples from Microsoft", location Redmond, WA.)

• audits

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

• freshness

  100/100
  • ✓ Last shipped: last commit 3d 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 Typechat, 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.