Repository navigation
crypto-agility manifest: spec + qScan emit/validate (frontier #13) - #40
Merged
Merged
Conversation
Add the crypto-agility manifest (roadmap frontier initiative 13, MVP): a well-known-URL JSON document (/.well-known/crypto-agility.json) that publishes a project's crypto posture so any agent, scanner, or CI bot can read it like security.txt. - core: buildCryptoAgilityManifest + validateCryptoAgilityManifest (zero-dep, hand-rolled JSON + validation). The manifest is derived from a scan's inventory and CBOM: version, generatedAt, posture (readiness score, hybrid-KEX assertion, quantum-vulnerable findings by severity, HNDL-exposed count), cbomSummary (families in use, asset count, CBOM serial), optional attestation URL, and policy (NIST IR 8547 2030/2035 by default, or an operator transitionDeadline). - qscan: 'crypto-agility emit' / '--crypto-agility' (additive, always exits 0) and 'crypto-agility validate <file>' (exit 0 valid / 1 invalid / 2 I/O). Validator is strictly offline; a remote fetch-and-validate is a website-side follow-up. - docs/CRYPTO-AGILITY-MANIFEST.md spec, help text, CHANGELOG, regenerated API surface. - Unit tests for emit shape and validate accept/reject; action bundle rebuilt. Purely additive: detectors, detection F1 = 1.000, existing report formats, and scan exit codes unaffected.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Frontier initiative #13 MVP. A well-known-URL manifest so any agent, scanner, or CI bot can read a project's crypto posture like security.txt.
docs/CRYPTO-AGILITY-MANIFEST.md(version 1): served at/.well-known/crypto-agility.json. Fields: subject, posture (readiness score, hybrid-KEX-in-use as an operator-assertable null-by-default since a static scan cannot observe a negotiated group, quantum-vulnerable counts by severity, HNDL-exposed count), cbomSummary (algorithm families, links to the full CBOM), optional attestation url (recorded, never fetched), and policy deadlines (NIST IR 8547 default: deprecate classical 2030, disallow 2035).qscan crypto-agility emit [path]/qscan ./ --crypto-agility(stdout or -o), additive, always exit 0.qscan crypto-agility validate <file>, strictly offline (local file only; a network fetch-and-validate + an MCP reader are documented follow-ups for the website side).Verification: all tests pass (+16), benchmark F1 = 1.000, typecheck/lint/format clean, api:check matches (api docs regenerated), action dist rebuilt. Manual-merge per repo guardrail.