Skip to main content

voltry-evidence-schema

The Voltry evidence bundle: the signed contract behind every Voltry Probe scan and certificate.

Note the naming: the PyPI distribution is voltry-evidence-schema, the Python package you import is evidence_schema.

pip install voltry-evidence-schema
import evidence_schema

What it provides

  • Typed pydantic v2 models (EvidenceBundle and its blocks). The bundle carries measured facts only (there is no modeled-estimate type in this package), no single score anywhere, and no price field.
  • One canonical serializer: RFC 8785 (JCS) over the bundle minus its signature. This is the only path to signable bytes.
  • ECDSA P-384 (secp384r1) with SHA-384 sign and verify over those canonical bytes.
  • A generated JSON Schema for cross-language consumers.

Verifying a bundle

To check a stored bundle as a third party, verify the raw bytes exactly as they were stored. This is the version-stable path: it reproduces the bytes that were signed no matter which schema version signed them, so a bundle signed years ago under an older 1.x still verifies today.

from evidence_schema import verify_bundle_json

raw = open("bundle.json", "rb").read()  # the stored bytes, unmodified
print(verify_bundle_json(raw))  # True only if the signature covers these exact bytes

A True result proves integrity: the bundle is byte-identical to what the holder of the embedded public key signed. It does not prove that key belongs to an authorized signer; binding keys to registered operators is the platform's job, checked against the Voltry registry.

Command line:

# Round-trip demo: build, canonicalize, sign, verify, tamper, verify fails
python -m evidence_schema.demo

# Emit the JSON Schema for non-Python consumers
evidence-schema-jsonschema -o evidence_bundle.schema.json

Stability

The schema is versioned semantically, and a bundle captured today remains valid and verifiable indefinitely: the 1.x field set only ever grows, existing fields never change meaning, and verification runs over the raw stored bytes so later schema versions cannot disturb it. Additive fields are minor versions; anything breaking is a major version with a migration path. Canonical bytes are covered by golden-vector tests in CI on Python 3.10 (the supported floor) and 3.12; the package supports 3.10 through 3.13.

Security

To report a vulnerability, see SECURITY.md.

License

Apache-2.0.

Release files for voltry-evidence-schema 1.2.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for voltry-evidence-schema 1.2.2
File Size Uploaded
voltry_evidence_schema-1.2.2.tar.gz 47.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for voltry-evidence-schema 1.2.2
File Interpreter ABI Platform
voltry_evidence_schema-1.2.2-py3-none-any.whl Python 3 none any Details

Total release size: 77.7 kB

Release files / voltry_evidence_schema-1.2.2.tar.gz

Download URL voltry_evidence_schema-1.2.2.tar.gz
Size 47.6 kB
Tags Source
SHA-256 checksum
How to use checksums
546020e82f296a00d076ca2bb1cd93c0a02916a04b8ab4434ef754e4d94f5e21
BLAKE2b-256 checksum
How to use checksums
67c4fa794e09517a084a3d521c5e3bb565bd20a53e2e3aff8f63f3da3ad87b40
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Jul 12, 2026.

Transparency log

Release files / voltry_evidence_schema-1.2.2-py3-none-any.whl

Download URL voltry_evidence_schema-1.2.2-py3-none-any.whl
Size 30.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f03b6e41afc01b9c7825011107d06da34284c49026f881d027142797c428371d
BLAKE2b-256 checksum
How to use checksums
dd1a2afde789fdc2ff90d5dd3c9f3cae23f6dd188bf45acc2d21ef1ecc9d6db5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Jul 12, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.2.2 This release

2 release files

1.2.1

2 release files

1.2.0

2 release files

1.1.0

2 release files

1.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page