Sato Hub
Score history

Neuronto Payments

One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.

Score today

66

Change over 47d

+3

Days measured

47

Days missed

0

Sato Score, daily

2026-10-05 → 2026-11-20
02550751002026-10-05: 63 (Medium)2026-10-06: 63 (Medium)2026-10-07: 63 (Medium)2026-10-08: 63 (Medium)2026-10-09: 63 (Medium)2026-10-10: 63 (Medium)2026-10-11: 63 (Medium)2026-10-12: 63 (Medium)2026-10-13: 63 (Medium)2026-10-14: 63 (Medium)2026-10-15: 63 (Medium)2026-10-16: 63 (Medium)2026-10-17: 63 (Medium)2026-10-18: 63 (Medium)2026-10-19: 64 (Medium)2026-10-20: 64 (Medium)2026-10-21: 64 (Medium)2026-10-22: 64 (Medium)2026-10-23: 64 (Medium)2026-10-24: 64 (Medium)2026-10-25: 64 (Medium)2026-10-26: 64 (Medium)2026-10-27: 64 (Medium)2026-10-28: 64 (Medium)2026-10-29: 64 (Medium)2026-10-30: 64 (Medium)2026-10-31: 64 (Medium)2026-11-01: 64 (Medium)2026-11-02: 66 (Medium)2026-11-03: 66 (Medium)2026-11-04: 65 (Medium)2026-11-05: 66 (Medium)2026-11-06: 66 (Medium)2026-11-07: 66 (Medium)2026-11-08: 66 (Medium)2026-11-09: 66 (Medium)2026-11-10: 66 (Medium)2026-11-11: 66 (Medium)2026-11-12: 66 (Medium)2026-11-13: 66 (Medium)2026-11-14: 66 (Medium)2026-11-15: 66 (Medium)2026-11-16: 66 (Medium)2026-11-17: 66 (Medium)2026-11-18: 66 (Medium)2026-11-19: 66 (Medium)2026-11-20: 66 (Medium)6366662026-10-052026-11-20

Every day in this span has a reading. A dashed vertical mark (┆) is a day Sato Hub changed the scoring method — movement on those days is ours, not the project’s.

Every day the score moved

4 changes attributable to the project, 0 caused by a revision of the scoring method.

DateFromToChangeCause
2026-11-056566+1the project
2026-11-046665-1the project
2026-11-026466+2the project
2026-10-196364+1the project

What moved, component by component

Six charts, six axes — each scaled to its own maximum weight. They are never stacked on one axis: a component worth 10 points and one worth 35 would not be comparable on a shared scale, and the small one is usually the one that moved.

Maintenance & liveness35/35
35
Code transparency0/20
20
Interface verifiability10/10
10
Docs & demo6/10
10
Listing transparency & provenance12/15
15
Independent verification3/10
10

The observed record

100% of 47 daily checks since 2026-10-05 succeeded. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side. When a check before 2026-09-01 failed, the checks before that date are left out of the rate: the probe counted a bot-block as a failure then and recorded no reason for any failure.

2026-10-05: answered our check2026-10-06: answered our check2026-10-07: answered our check2026-10-08: answered our check2026-10-09: answered our check2026-10-10: answered our check2026-10-11: answered our check2026-10-12: answered our check2026-10-13: answered our check2026-10-14: answered our check2026-10-15: answered our check2026-10-16: answered our check2026-10-17: answered our check2026-10-18: answered our check2026-10-19: answered our check2026-10-20: answered our check2026-10-21: answered our check2026-10-22: answered our check2026-10-23: answered our check2026-10-24: answered our check2026-10-25: answered our check2026-10-26: answered our check2026-10-27: answered our check2026-10-28: answered our check2026-10-29: answered our check2026-10-30: answered our check2026-10-31: answered our check2026-11-01: answered our check2026-11-02: answered our check2026-11-03: answered our check2026-11-04: answered our check2026-11-05: answered our check2026-11-06: answered our check2026-11-07: answered our check2026-11-08: answered our check2026-11-09: answered our check2026-11-10: answered our check2026-11-11: answered our check2026-11-12: answered our check2026-11-13: answered our check2026-11-14: answered our check2026-11-15: answered our check2026-11-16: answered our check2026-11-17: answered our check2026-11-18: answered our check2026-11-19: answered our check2026-11-20: answered our check
  • answered
  • host answered with an error
  • failed on our side
  • failed, unattributable

Every reading

The table the charts are drawn from. A missing day is missing from this table too — nothing is filled in.

DateScoreTierStatusOur check
2026-11-2066MediumUnknownup
2026-11-1966MediumUnknownup
2026-11-1866MediumUnknownup
2026-11-1766MediumUnknownup
2026-11-1666MediumUnknownup
2026-11-1566MediumUnknownup
2026-11-1466MediumUnknownup
2026-11-1366MediumUnknownup
2026-11-1266MediumUnknownup
2026-11-1166MediumUnknownup
2026-11-1066MediumUnknownup
2026-11-0966MediumUnknownup
2026-11-0866MediumUnknownup
2026-11-0766MediumUnknownup
2026-11-0666MediumUnknownup
2026-11-0566MediumUnknownup
2026-11-0465MediumUnknownup
2026-11-0366MediumUnknownup
2026-11-0266MediumUnknownup
2026-11-0164MediumUnknownup
2026-10-3164MediumUnknownup
2026-10-3064MediumUnknownup
2026-10-2964MediumUnknownup
2026-10-2864MediumUnknownup
2026-10-2764MediumUnknownup
2026-10-2664MediumUnknownup
2026-10-2564MediumUnknownup
2026-10-2464MediumUnknownup
2026-10-2364MediumUnknownup
2026-10-2264MediumUnknownup
2026-10-2164MediumUnknownup
2026-10-2064MediumUnknownup
2026-10-1964MediumUnknownup
2026-10-1863MediumUnknownup
2026-10-1763MediumUnknownup
2026-10-1663MediumUnknownup
2026-10-1563MediumUnknownup
2026-10-1463MediumUnknownup
2026-10-1363MediumUnknownup
2026-10-1263MediumUnknownup
2026-10-1163MediumUnknownup
2026-10-1063MediumUnknownup
2026-10-0963MediumUnknownup
2026-10-0863MediumUnknownup
2026-10-0763MediumUnknownup
2026-10-0663MediumUnknownup
2026-10-0563MediumUnknownup

What happened alongside it

Releases, status changes, applied corrections and answered disputes, on the same dates — so a movement in the line can be read against an event rather than guessed at.

  1. Oct 5, 2026
    Auto-enriched: chains supported, tags, supported integrations, has pricing +2 more
  2. Oct 5, 2026
    Listed on Sato Hub
  3. Oct 5, 2026
    Sato Hub began tracking this listing

How to read this

  • · Every point is one UTC day. A day we did not capture is drawn as a gap, never joined across.
  • · A change on a marked methodology day is ours, not the project’s.
  • · The score says how open, active and verifiable the project is. It is not a safety, quality or returns grade.
  • · The inputs behind today’s score are published at /api/export/score-inputs.json and the arithmetic is reproducible on your own machine.