How packages are verified
Fingerprints
Every agent version has a SHA-256 fingerprint covering everything that defines it: instructions, settings, tools, connected services and the hash of every playbook and file it ships. The fingerprint is fixed the moment a version is listed. A listed version can never change; changes are released as a new version with a new fingerprint.
Before every deployment, the deployment platform recomputes the fingerprint and refuses to deploy a package that no longer matches its listing.
Signed catalogue
The list of agents and their fingerprints (catalog.json) is signed with the publisher's Ed25519 key. Your browser checks the signature before showing any listing; if the check fails, no agents are displayed.
- Algorithm
- Ed25519
- Publisher key ID
- loading…
- Public key
- publisher-key.pem · publisher-key.json
- Signature
- catalog.json.sig (64 raw bytes)
Check it yourself
Download the catalogue, its signature and the public key, then verify with OpenSSL 3:
OpenSSL prints Signature Verified Successfully when the catalogue is authentic. Compare the key ID above with the one your provider gave you through a separate channel: a signature only proves authenticity if you trust the key.