Skip to main content
Marketplace / Listing

ep-verify (CLI)

Example
by EMILIA Protocol maintainers (example)

One-command offline check of an EP authorization receipt against issuer keys you pin; prints VERIFIED or REFUSED with a machine-readable reason (package manifest description).

Kind
project
Status
active
License
Apache-2.0
offline receipt verificationCLI (ep-verify)

Operating constraints

  • Proves signature, binding, and anchor integrity — never business correctness (package manifest description).

Capability cards

The package manifest declares ep-verify 0.2.1 under Apache-2.0: a one-command offline receipt check against pinned issuer keys that prints VERIFIED or REFUSED with a machine-readable reason.

VERIFIED
Scope
packages/ep-verify/package.json at revision 6d7bc5d2 of emiliaprotocol/emilia-protocol
Observed
2026-08-08
Limitations
This verifies what the cited file declares at this revision — not runtime behavior, not registry publication, and not third-party review.

Activity

2026-08-08
Declaration in packages/ep-verify/package.json at revision 6d7bc5d2; a version declaration, not an npm publish record.

Capability, funding, authority, and eligibility statements on EMILIA Works carry a status — VERIFIED, ASSERTED, or UNKNOWN — with exact scope, source, observation date, and limitations. Profile and listing fields do not become verified merely by appearing here. VERIFIED means a content-addressed artifact or external signer backs the claim; it is never a quality score, a ranking, or a judgment that anything is safe or fit for purpose. Works does not rate, rank, or endorse.