Verification record
Enso
Its Sato Hub Sato Score and verification record — how open, active, and verifiable this product is, scored from observed evidence. Not a safety, quality, or returns grade.
Sato Score
70/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 25/35
- Code transparency
- 13/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 15/15
- Independent verification
- 3/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Anchored
2026-09-20 · 384 listingsThis score was committed to a single Merkle root along with every other score we published that day. The root is signed, published, and archivable by anyone — so if we changed this number tomorrow and said it had always been this, the commitment would contradict us. It proves what we published, not that the score is right.
- Leaf
eedc1a9fca6ebbf70792e0296ed5ffe4b779d2f79e6c30dfe2bc94ddc48c499e- Preimage
satohub-score-leaf/v1|2026-09-20|enso-shortcuts|70|High- Proof
- 8 siblings
- Root
5216b3a5352d78176f3ae7d63b91f40d2be917b01afaf0942fc8dd95f9fe48a9- Root signature
- Ed25519, kid b04bd38b
- On-chain
- not attested on-chain — key absent (ATTEST_PRIVATE_KEY is not set)
Verify this yourself
# one command, no install, no account
npx --yes github:satohubai/sato-hub-skill \
node skills/sato-hub/scripts/verify.mjs --proof enso-shortcuts --date 2026-09-20The tool folds the proof itself and compares the result against the published roots file, not against the proof response — checking a proof only against a root served in the same reply proves nothing. Raw proof: /api/verify/enso-shortcuts/proof. Method: the house rules.
Evidence
- ✓Deploy path reproduced in an isolated container (docker:node:22-bookworm-slim) on Sep 7, 2026: install passed, entry passed. Verifies installability, not runtime safety or on-chain behavior.
- ▸Source reviewed ↗
Record
- Last checked
- 2026-09-20
- Last observed activity
- Jul 14, 2026
- Methodology
- Sato Score methodology →
Verification history
A dated, auditable record of every change to this listing's status, verification, and Sato Score.
- Sep 7, 2026Verified: deploy spec
- Sep 1, 2026Sato Score tier: Medium → HighScore 67 → 70.
- Aug 14, 2026Sato Score tier: High → MediumScore 77 → 67.
- Jul 15, 2026Sato Score tier: Medium → HighScore 67 → 77.
- Jun 25, 2026Auto-enriched: creator name, x url, supported integrations, deployment options +1 more
- Jun 19, 2026Sato Hub began tracking this listing
Embed this badge
[](https://satohub.ai/verify/enso-shortcuts?utm_source=badge&utm_medium=embed)Paste into your README. The badge reflects the live Sato Score and links back to this report. Free to use, no attribution required.
Embed the 90-day history
[](https://satohub.ai/verify/enso-shortcuts/history?utm_source=badge&utm_medium=embed)Paste into your README. The sparkline is the last 90 days of daily Sato Score readings with the 90-day change; days nobody measured are drawn as gaps, never joined across. It links back to the full dated record. Free to use, no attribution required.
Think this score is wrong?
Check it first: every input behind it is published at /api/export/score-inputs.json and the scorer is a verbatim copy of ours, so the arithmetic can be run on your own machine — reproduce this score. If you maintain Enso and still disagree, say so in public: a dispute is published with your evidence beside our answer, whether or not we agree with it.