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

How Vanna scored a C.

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.

C
51/100

GitHub credibility score

  • code

    42/100
    • Contributors & bus-factor: 5 recent contributors — concentrated
    • Commit recency: last commit 220d ago
    • Commit cadence: 0 commits in 90 days
    • Issue close ratio: 56% of issues closed
    • Release cadence: 4 releases in 12 months
    • Stars (log-damped): 23,815 stars (log-damped)
    • Star authenticity: star-velocity check unavailable — GitHub no longer publishes stargazer timestamps for this repo
    • Dependent repos: not measurable — no package listing on a registry we can query
  • identity

    Not measured
    • Identity: no verified provenance yet
  • audits

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

    72/100
    • Last shipped: last release 220d 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 Vanna, 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.