Repository navigation
docs(fido): publish FIDO conformance self-validation results #396
Description
Why
Self-validation ran (#172). Publishing the results is cheap proof for the most-secure promise, and comes before paying for certification.
What
- Publish the test tool version, the date, the results per test suite and any known deviations
- Link from the security posture page
Acceptance
- Tool version and date of each run, and pass or fail per suite
- Known deviations, including that SafetyNet attestation cannot be fixture tested (the tools never emit it)
- A note that interoperability testing and certification are deferred to v1.0 (chore(fido): interoperability testing and Functional Certification submission #397)
Done when
Results are published and linked, worded as self-validation, not certification.
Activity
Bccorb commentedon Oct 20, 2026
Plan: this is the last step of v0.19. The September run left the capture and fixtures but not the conformance tool's own report, so the self-validation runs again against the final v0.19 code with the tool's report exported (tool version, date, pass or fail per suite). These results are published from that export and linked from the docs security page (fells-code/seamless-auth-docs#120).