Know what is current.
ScriptMasterLabs CANON answers whether an artifact is still current and what the publisher verifiably says now, resolving live npm and PyPI versions against signed Ed25519 publisher manifests. It returns one of six verdicts — fresh, stale, tampered, conflict, superseded/withdrawn/deprecated, or unknown — and never invents consensus. Bulk audits cover up to 100 items at 0.01 USDC per accepted bulk delivery.
CANON resolves a simple machine question that mirrors and cached metadata often cannot answer: is this artifact still current, and what does the publisher verifiably say now?
Runtime contractMachine product card
Where does CANON get live version evidence?
Resolve current npm and PyPI package versions from their public registries. Registry-owned facts remain registry authority.
How does CANON verify publisher truth?
Verify Ed25519 publisher manifests, expiry, key activation and monotonic sequence state before trusting publisher intent.
What happens when publisher and registry disagree?
If a verified publisher version disagrees with a live registry version, CANON returns conflict. It does not invent consensus.
How does CANON audit mirror drift?
Audit stale mirrors and held versions against live registry state. Version matches can also be checked against integrity evidence when available.
What verdicts can CANON return?
CANON returns one of six verdicts: fresh, stale, tampered, conflict, superseded / withdrawn / deprecated, or unknown.
| Verdict | Meaning |
|---|---|
fresh | The held version matches the current resolved version. |
stale | The held or mirrored version trails current resolved evidence. |
tampered | Version matches but supplied integrity evidence conflicts with expected integrity. |
conflict | Verified publisher and live registry disagree; CANON does not choose a winner automatically. |
superseded / withdrawn / deprecated | Verified publisher state or registry evidence explicitly carries that condition. |
unknown | The available evidence is insufficient for a stronger conclusion. |
How do you use CANON?
CANON’s core registry resolver needs no subscription and no model or API key.
How do you run a free single lookup?
A single GET resolves one package and held version against the live registry.
GET https://squeezeos-api.onrender.com/api/canon/resolve?id=@scriptmasterlabs/mcp-x402&held_version=2.1.3No subscription. No model/API key required for CANON's core registry resolver.
How do you audit a mirror for free?
One GET call checks a mirror’s held version against live registry state.
GET https://squeezeos-api.onrender.com/api/canon/audit-mirror?package=@scriptmasterlabs/mcp-x402&mirror_version=2.1.3How do you inspect a publisher?
One GET call inspects a publisher’s manifest signature trust, expiry, anti-rollback sequence state, and registry drift.
GET https://squeezeos-api.onrender.com/api/canon/manifest?domain=scriptmasterlabs.comChecks manifest signature trust, expiry, anti-rollback sequence state and registry drift.
How does x402 bulk resolution work?
One POST call resolves up to 100 items, at 0.01 USDC per accepted bulk delivery on x402 v2 over Base mainnet.
POST https://squeezeos-api.onrender.com/api/canon/batchUp to 100 items. 0.01 USDC per accepted bulk delivery. x402 v2 on Base mainnet. Validation and resolution preflight occur before the payment gate.
What does the CANON publisher protocol require?
A participating publisher exposes /.well-known/canon.json and /.well-known/canon-keys.json. CANON verifies an Ed25519 signature, key validity, expiry and sequence monotonicity before publisher claims can affect the result.
Provider: SCRIPTMASTERLABS · Legal entity: Script Master Labs, LLC · Truth First. Proof Always. Pay Only for Accepted Delivery.