This is an early release preview. You may encounter bugs.
← OpenSpec

How OpenSpec scored an A.

A way.space signal summary built from public evidence. It is not a user rating, and not a safety certification. How scores are calculated.

01 / Breakdown

Derived from GitHub, not voted.

A
84/100

GitHub credibility score

  • code

    77/100
    • ✓ Contributors & bus-factor: 38 recent contributors
    • ✓ Commit recency: last commit 1d ago
    • ✓ Commit cadence: 314 commits in 90 days
    • ✓ Issue close ratio: 83% of issues closed
    • ✓ Release cadence: 39 releases in 12 months
    • ✓ Stars (log-damped): 72,933 stars (log-damped)
    • ↓ Star authenticity: engagement of 0.10 per star — star signal discounted by 11%
    • ↓ Dependent repos: no public repos depend on it yet
  • identity

    Not measured
    • – Identity: no verified provenance yet
  • 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

    82/100
    • – Recommends: no recommends from gate-passing builders yet
    • ✓ Hacker News mentions: 11 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 OpenSpec, 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.