Sato Hub

Methodology

The Sato Score

A transparent, evidence-based score (0–100) of how open, active, and verifiable a listed product is. Transparency is one of several inputs — alongside maintenance & liveness, code openness, documentation, and independent verification.

It measures how open, active, and verifiable a project is — not safety, quality, or returns.

A high score does not mean a project is safe, audited, profitable, or a good investment. It means we can verify a lot about it. A low score often just means a project is new, private, or thinly documented — not that it is bad. The score is informational, not financial advice or an endorsement.

This honesty is deliberate: per our trust rule, no resource is presented as safe, audited, verified, or profitable unless evidence supports it, and self-reported claims are never counted as verified.

What goes into the score (v1)

The score sums five evidence-based components. Each is computed deterministically from observed data — not from a project’s own marketing.

Maintenance & liveness

max 35

Recency of observed activity (commits, releases, posts). Uses real activity, not the self-applied “Active” label.

Code transparency

max 25

Public repository, open-source status, and a light adoption signal (stars).

Docs & demo

max 15

Whether documentation and a working demo exist.

Listing transparency & provenance

max 15

How complete the listing is and how much of it is sourced — every enriched field carries provenance.

Independent verification

max 10

Evidence-gated only: Verified or Audited. Self-reported claims earn nothing.

Tiers

High70–100
Medium40–69
Low0–39

What is deliberately not in the score yet

We do not fake what we cannot verify. These are roadmapped components, scored zero today and added only as their evidence becomes available — at which point scores recalibrate (this is v1):

How it’s computed and kept honest

See the Sato Score in context across the ecosystem.Browse verified resources →