How Flint Chart scored a B.

• code

  63/100
  • ✓ Contributors & bus-factor: 2 recent contributors — concentrated
  • ✓ Commit recency: last commit 28d ago
  • ✓ Commit cadence: 423 commits in 90 days
  • ✓ Issue close ratio: 41% of issues closed
  • ✓ Release cadence: 6 releases in 12 months
  • ✓ Stars (log-damped): 4,180 stars (log-damped)
  • ↓ Star authenticity: engagement of 0.09 per star — star signal discounted by 17%
  • – Dependent repos: not measurable — no package listing on a registry we can query

• identity

  80/100
  • ✓ Organisation: Built by Microsoft · notable organisation (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: not measurable — no registry listings for this tool

• freshness

  100/100
  • ✓ Last shipped: last release 28d ago — standard-churn tools are expected to ship about every 120d

• 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 Flint Chart, 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.