Test vectors
Draft - coming soon
The formal conformance suite and its certification program are still in development. The test-vector corpus described here is a draft and not yet a stable, published release.
The conformance suite ships a corpus of signed test vectors. Every SDK and the CLI are validated against it on each release, and third-party implementations must pass it to claim conformance.
Get the corpus
bash
osdf conformance fetch --out ./vectorsosdf conformance run ./vectorsCategories
| Category | Expectation |
|---|---|
valid/ | Verifies cleanly at the declared profile |
tampered/ | Integrity or signature failure |
malformed/ | Container rejected before parsing content |
rollback/ | Freshness failure against cached checkpoint |
revoked/ | Policy failure due to revocation |
offline/ | Verifies from embedded evidence with no network |
Expected outcomes
Each vector ships an expected.json describing the required per-stage result:
json
{ "vector": "tampered/body-byte-flip", "expect": { "structure": "pass", "signature": "fail" }, "must_render": false}Determinism
A conforming implementation must produce the same per-stage verdict for every vector. Non-deterministic results are a conformance failure.