Expand description
The deep verification entry: one interface for every surface.
The Pipeline is the ordered hard/soft check engine, but its
constructor takes every dependency as a raw parameter, so each
transport adapter (browser WASM, HTTP, CLI, Python) used to
re-assemble the same wiring — a verifier fleet, a revocation view,
transparency inputs, an acceptance policy — just to reach it.
This module owns that assembly once.
use confium_signatif::verify::{verify_trusted_artifact, VerifyOptions};
let options = VerifyOptions {
transparency_included: true,
accepted_labels: vec!["verified".into()],
..VerifyOptions::default()
};
let verdict = verify_trusted_artifact(&artifact, &bundle, &graph, ®istry, &options)?;
assert!(verdict.accept);Revocation checking currently runs with
NoRevocations; this
function is the single place that changes when a surface grows a
revocation input. Schemes that need a CrlView
today assemble the Pipeline directly.
Structs§
- Verdict
- The graduated verification outcome: the objective coverage report, the scheme’s classification label, and this verifier’s acceptance decision — the triple every surface serializes.
- Verify
Options - The verification inputs a transport collects, in the shape every surface already speaks: field names match the JSON options of the HTTP endpoint, the browser binding, and the CLI flags.
Enums§
- Fleet
- Which signature algorithms a verifier checks.
Functions§
- verify_
trusted_ artifact - Verify one trusted artifact through the full pipeline.