Updated Oct 16, 2026

Utilities

Verify an Ed25519 passport receipt with an explicit key

veritas-verify is an Ed25519 passport-receipt verification node that uses an explicit supplied public key.

Agent

overview

What veritas-verify does

Supply a JSON passport receipt and an explicit 64-character hexadecimal Ed25519 public key. The native Veritas verifier returns a JSON integrity report against that key. A supported receipt contains an object payload and a signature object with alg, kid and a 128-character hexadecimal sig.

Receipt input is limited to 1 MiB, native execution to 30 seconds, Node heap to 256 MiB and output to 4 MiB. The fixed operation uses receipt mode only, with no JWKS URL, credential or daemon. Input files remain unchanged.

Tampering or a wrong key produces successful task output with valid: false and invalid_signature. Malformed JSON, unsupported receipt shapes and other verifier failures fail the task. Inspect valid separately from node success.

This operation uses 0.10.21. Upstream license: Apache-2.0. The source link identifies the program used by this node.

source github.com/VeritasActa/verify/tree/5ab70b3c0ada4806e156fe1c6f8394df58333d1f

use cases

Where veritas-verify fits

Check receipt integrity

Verify a supported receipt against a public key you supply.

Detect changed payloads

Inspect valid: false when a payload or verification key does not match.

Keep key selection explicit

Choose the verification key explicitly rather than relying on remote key discovery.

reference

veritas-verify inputs and flags

2 inputs
NameTypeFlagDescription
inputFILE--inputJSON passport receipt with object payload and hex Ed25519 signature, up to 1 MiB.
public-keySTRING--public-keyExplicit verification public key, exactly 64 hexadecimal characters. Caller is responsible for trusting this key.

Showing key inputs. veritas-verify exposes 2 inputs in total.

example

Run veritas-verify

veritas-verify · command
node /app/run.mjs --input ./input.txt --public-key PUBLIC_KEY_HEX ./output
sample output
{
  "valid": true,
  "keySource": "provided",
  "format": "passport",
  "kid": "fixture-ed25519",
  "canonicalization": "jcs"
}

guidance

Choosing veritas-verify

Use this node to check receipt integrity against a key you have chosen to trust. A valid signature does not establish signer trust or prove that the signed claims are true.

OpenSSH ssh-keygen

Fingerprints or operates on SSH keys; it does not verify this passport receipt format.

faq

veritas-verify questions

input: JSON passport receipt with object payload and hex Ed25519 signature, up to 1 MiB. public-key: Explicit verification public key, exactly 64 hexadecimal characters. Caller is responsible for trusting this key.

JSON signature result. Tampering or a wrong key produces successful task output with valid: false and invalid_signature. Malformed JSON, unsupported receipt shapes and other verifier failures fail the task. Inspect valid separately from node success.

Receipt input is limited to 1 MiB, native execution to 30 seconds, Node heap to 256 MiB and output to 4 MiB. The fixed operation uses receipt mode only, with no JWKS URL, credential or daemon. Input files remain unchanged.

Use this node to check receipt integrity against a key you have chosen to trust. A valid signature does not establish signer trust or prove that the signed claims are true.

The image repository also contains a digest-bound source/notices artifact. Download it with oras pull docker.io/nenadzaric/skills-intel-veritas-verify@sha256:f6ba776a3aa95fec5e8316d1d13bdf71490764f960a73dde13f12f8ea8596182. The bundle includes the build recipe, licenses, copied notices and component-source directions. Bundle SHA256: 3e51a5350f871729c322c365dd5c2eaf0f033e7e84c76b1a3d6e4fd072c5108c. Follow its source directions for upstream archives and patches. Image and source/notices repository.

Run veritas-verify yourself

The synthetic run checks json signature result. The excerpt shows selected native fields asserted by saved passing platform verifier; reconstructed excerpt, not full raw artifact. The command shown is the container entrypoint with example paths, not a host-installed CLI command.

Facts on this page come from the live Trickest tool library.