verifyanything
VerifyAnything DRAFT wire SDK for python. Independently versioned package 0.1.0, intended registry: PyPI. Names/ownership must be confirmed before publication.
VCP means portable verification semantics; Provider Contract means the portable verifier interface; Relay is the separate Python reference execution engine.
This SDK bundles every normative VCP/Provider schema at source revision
5f17f402a270882f244a54dde25eda92a085eb39. VCP marker: draft;
Provider Contract: exact 0.1. Both remain DRAFT with no stable 1.0 promise.
Validation does not fetch schemas, artifact content or URLs.
from verifyanything import parse, serialize
value = parse('vcp', 'decision', '{"protocol":"draft","kind":"CONTINUE"}')
print(serialize(value))
Actual support
The public wire object is a native JSON object view, retaining absent fields, explicit null payloads and unknown optional extensions. It is not a complete generated field-by-field static model of every protocol object. Structure-only validation covers all shipped schema roots. Parse/semantic validation supports Result, Decision, Resource, Evidence, ArtifactRef, Extension and ResourceDimension. It checks Result state axes, Decision destinations, meaningful Evidence, resource kinds/ranges, required extensions and nested evidence/usage/extensions.
Provider standalone validation covers manifest structure, capability identity
uniqueness and advertised VCP membership, self-contained capability schemas,
Outcome state/output/error conditionals, and invocation version/resource-budget
checks. validateData (snake_case in Python/Ruby/Rust) validates capability
input, config or output with an explicit error classification; formats are
annotations. There is no implicit capability matching or session initialization.
Semantic validation of graphs, definitions, profiles, execution-policy objects,
dataflow and provenance is not implemented in these new wire libraries.
It fails with the local diagnostic SDK_UNSUPPORTED; callers may explicitly
request structure-only validation. Provider session/lifecycle, transport,
deadline enforcement and contextual invocation matching are also unimplemented.
Parsing objects carrying deadline/timestamp fields fails with SDK_UNSUPPORTED;
call structure-only validation if that explicit limitation is acceptable.
Standalone parsing does not establish those properties. Detailed support/gaps and
release gates are in the repository's sdk/README.md and sdk/RELEASE.md.
Errors expose stable codes where the source contract specifies them. Decision rejection uses a local structural classification because the source prose does not specify a Decision-specific diagnostic. No portable canonicalization or hashing is claimed. Serialize preserves data and inserts no schema defaults. Mutable native containers must be validated again after mutation.
Build and test
From this directory: python -m pip install -e . pytest && python -m pytest.
From the source repository root: python tools/sdk_verify.py python runs the
native runner over the same versioned conformance/sdk/manifest.json, builds
twice, compares package file contents and installs into a separate consumer.
Dependency installation can use the network; actual schema validation is offline.
The shared corpus is a bounded compatibility test, not full protocol certification.
This independently packaged wire-only library uses module verifyanything and
project verifyanything. The original openverify Python distribution and its
Relay API remain unchanged. Both are checked against the common fixtures.
Release
Tag only this language: sdk/python/vX.Y.Z after updating only its package.
The protected release environment is sdk-python. First publication requires
owner setup and explicit approval; no package has been published by this change.
License: MIT (included in the distribution).
Package setup: VerifyAnything publication guide.
Metadata
Release files for verifyanything 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| verifyanything-0.1.0.tar.gz | 24.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| verifyanything-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 46.0 kB
Release files / verifyanything-0.1.0.tar.gz
| Download URL | verifyanything-0.1.0.tar.gz |
|---|---|
| Size | 24.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
218e3d07dd4457758c830cab0e43eae60226652b6c31a8eff6f58f50e1f8bfbc
|
|
BLAKE2b-256 checksum How to use checksums |
a34a24b4d2ececd9860293477687ee3cc3fc3812c68979d60bc30aefda292f05
|
| 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 Oct 20, 2026.
Transparency logRelease files / verifyanything-0.1.0-py3-none-any.whl
| Download URL | verifyanything-0.1.0-py3-none-any.whl |
|---|---|
| Size | 22.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5c52cdd28fa18c28a5258db5ef262706ec0666b02e0c5bd79fa5205fc484186e
|
|
BLAKE2b-256 checksum How to use checksums |
988698f3fa086aa0ed432c3d99c90b499f6f6a825f6c07d578a4fa3733f21596
|
| 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 Oct 20, 2026.
Transparency logSecurity for verifyanything 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for verifyanything-0.1.0.tar.gz
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 Oct 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.