ep-verify
One-line offline verifier for EMILIA Protocol authorization receipts
(EP-RECEIPT-v1). A thin CLI over emilia-verify,
so ep-verify is the same verb on PyPI and npm.
pip install ep-verify
ep-verify receipt.json --keys keys.json
Prints VERIFIED or REFUSED plus one machine-readable JSON line;
exit code 0 only on VERIFIED. Fully offline, fail closed: a missing key,
unreadable file, or verifier error is a refusal, never a pass.
What VERIFIED means: the Ed25519 signature over the canonical (RFC 8785) payload validates against a key you pinned, and any Merkle anchor is consistent. What it does NOT mean: that the action was correct, sufficient, or accepted by any relying party; acceptance is a relying-party decision.
Apache-2.0. Part of the EMILIA Protocol reference tooling: https://github.com/emiliaprotocol/emilia-protocol
1 maintainer
Metadata
1 maintainer
Release files for ep-verify 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ep_verify-0.2.2.tar.gz | 3.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ep_verify-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.8 kB
Release files / ep_verify-0.2.2.tar.gz
| Download URL | ep_verify-0.2.2.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
03da2356eda8df3a4ede8987051b7e2f631ba7cbd3647c88f9caf4428b6ae525
|
|
BLAKE2b-256 checksum How to use checksums |
6150f946629fe9a0585c721ce2496cb11974ef86b97c0a69ef93d4f7e2567967
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.
Transparency logRelease files / ep_verify-0.2.2-py3-none-any.whl
| Download URL | ep_verify-0.2.2-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8e37508824901ab9159f2c3bbf1de6f66bd0478abf53d3c943192bbe65f3162d
|
|
BLAKE2b-256 checksum How to use checksums |
0f5145d130e2f1484426371deaa0cea879f50afe2fe918ee4a75b01bf8d91ba8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.
Transparency log
