Implementations

Implementations of the framework

The standard defines requirements and conformance classes, not products. An implementation claims conformance to the classes it satisfies, witnessed by tests. Listing here is informational and does not imply endorsement, certification, or preference.

Signatif is implementation-neutral by design: every requirement class carries a matching conformance class so that "conforming implementation" is a testable claim, not a vendor assertion. Schemes and adopters choose implementations freely — including building their own.

Confium

Rust · browser/WASM · HTTP · CLI · Python

An open-source framework for multi-stakeholder threshold cryptography that implements the Signatif layer on top of its trust-graph, transparency, threshold-signing, and PKI components. Claims the full set of conformance classes, publishes a machine-generated conformance report guarded by CI, and ships an abstract-test-suite witness alongside scheme adoption tooling (registries, deployment manifests, multi-surface verification).

— Co-signed, multi-dimensional trusted artifacts
— Graduated verification pipeline with coverage reports
— Scheme-maintained registries, published and loadable
— JWS/JCS, COSE, and XMLDSig/Exc-C14N format profiles
— Classical, ML-DSA, SLH-DSA, and composite algorithms
— Hierarchical, federated, cross-recognized, mesh topologies

confium.org →Source →API documentation →

Getting listed

Any implementation satisfying one or more conformance classes may be listed. Open an issue or pull request against the site repository with the implementation's name, the classes claimed, and where the claims are witnessed (test suite, conformance report, or both). Listings state claims; they do not certify them — verification remains the reader's and the scheme's.