[AVAILABLE]. The offline verifier is a separate, public repository:
pavancharak/parmana-verifier,
Apache License 2.0. The Node version requires Node.js 24 or later and has no
dependencies. It is published on npm as
@parmana/verifier. A
Python version, for Python 3.11 or later, is published on PyPI as
parmana-verifier. Both are
version 2.0.0, published 2026-11-07. This is a breaking release: a record with
no schemaVersion, or with schema version 2, is refused unless the trust file
sets "allowLegacyV2": true (Python: allow_legacy_v2). To migrate, re-issue
the record as schema version 3.Run it
Install it, or run it without installing:parmana-verifier, use node bin/parmana-verify.mjs in place of parmana-verify.
Python
The Python version has the same checks, output and exit codes. It needs thecryptography
package. Install it from PyPI:
cryptography does not provide them.
A hybrid record is reported as invalid. Use the Node version to check those records.
proof.jsonis the Execution Trust Record.trust.jsonlists each key you accept:
0 when the record is valid, 1 when it is
invalid (with the reasons), and 2 for a usage error, a missing file or invalid JSON.
Pin a key
- Get the operator’s public key and the
sha256:fingerprint they published. Get the fingerprint from a source other than the one that gave you the key, such as a signed message. - Run
parmana-verify key-fingerprint public-key.pemon the PEM you received. - Compare the two fingerprints character by character. If they differ, do not use the key.
- Only then add the key to your trust file with that fingerprint.
Trust rules
A key is used only when all of these hold:- its PEM hashes to the pinned fingerprint (SHA-256 of the SPKI DER encoding);
- the algorithm named by the signature matches the algorithm in the trust file;
- it is not marked
compromised; - the record’s
createdAtis at or aftervalidFromand beforevalidUntil, if set.
Records with no hybrid envelope
A record with nosignatures array is refused unless one of these holds:
- the trust file sets
hybridRequiredFromand the record was created before that instant; - the trust file sets
"allowLegacyOnly": trueand does not sethybridRequiredFrom.
hybridRequiredFrom always needs a valid hybrid envelope. The default is refusal so that a removed envelope cannot pass unnoticed.
What it does not show
- It shows that a record was signed by the key you pinned. It cannot show that the key belongs to Parmana; that depends on how you obtained and compared the fingerprint.
- For schema version 2 records, only the fields listed in the repository’s format document are
protected. For schema version 3, every field except the signature envelope,
verificationsandreceiptsis protected. Check thatcoverageisfullwhen that matters. - It does not check the policy a record cites, the decision logic, or whether the action reached the external system.