cbomctl 0.1.0__tar.gz

cbomctl-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+.research/
+__pycache__/
+*.pyc
+.venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/

cbomctl-0.1.0/CHANGELOG.md

@@ -0,0 +1,67 @@
+# Changelog
+
+Semantic versioning. Policy-pack versions move independently — see
+[`policy-packs/CHANGELOG.md`](policy-packs/CHANGELOG.md).
+
+## [Unreleased] — 0.1.0
+
+First working version. **All seven policy packs are read from primary sources**
+— every rule cites the section or page it came from, names its verifier and
+pins the edition. The `UNVERIFIED POLICY PACK` banner, the `status` field and
+`--require-verified-policy` remain in place for the next rule that has not been
+checked, and are exercised by a synthetic test fixture.
+
+### Added
+- `cbomctl verdict` — per-asset × jurisdiction matrix plus a conflicts section
+  with a computed satisfies-all target. The product.
+- Conflict detection across four kinds: `construction`, `parameter`,
+  `deadline`, `scope`.
+- `cbomctl prioritize` — Mosca ranking from user-supplied data lifetimes.
+- `cbomctl plan`, `cbomctl normalize`, `cbomctl policies list|show`.
+- Purpose normalizer with an explicit precedence ladder, keeping `AMBIGUOUS`
+  and `UNKNOWN` distinct and never guessing between them.
+- Six policy packs as a standalone, semver-versioned artifact with their own
+  JSON schema, consumable without this tool.
+- Reporters: terminal matrix, JSON, Markdown, SARIF 2.1.0.
+- Composite GitHub Action; CI validates fixtures against the official CycloneDX
+  schemas and dog-foods the action on the conflict fixture.
+- Optional `--from sbom-tools` adapter, no dependency.
+
+### Design decisions worth knowing
+- **`binding` decides FAIL versus WARN, not severity.** A
+  `guideline_recommendation` cannot produce FAIL, enforced in code. Most PQC
+  guidance is guidance, and reporting it as law misinforms.
+- **`hybrid` is scoped per purpose and is a three-step gradient**:
+  `recommended` (BSI, ANSSI, EU) → `not_recommended` but permitted (ASD) →
+  `not_permitted_except_interop` (NSA). The middle step leaves a satisfies-all
+  target available at a cost; the third removes it, and the conflict output says
+  so rather than inventing a compromise.
+- **Urgency and assurance are separate axes.** BSI and ANSSI both recommend
+  hybrid *signatures* on algorithm-maturity grounds — ANSSI citing the classical
+  break of Rainbow — which is a different argument from
+  harvest-now-decrypt-later and reaches purposes HNDL cannot.
+- **Security strength is derived**, so NIST IR 8547's 112-bit 2030 deprecation
+  reaches RSA-2048 and P-224 but not RSA-3072 or P-256. Where it cannot be
+  derived the finding is indeterminate rather than the stricter date.
+- **Three ways to not answer**: `unscored` (purpose unresolvable),
+  `indeterminate` (a rule needs an undeclared fact), `not-applicable`. None is a
+  silent pass.
+- **`--strict`** turns every unverified rule into INDETERMINATE, so nothing
+  built on stub packs can be mistaken for a real verdict.
+  **`--require-verified-policy`** refuses to run at all.
+- **The CNSA 2.0 January 2027 acquisition gate is off by default**
+  (`--cnsa-acquisition-gate`): it is a procurement condition on new NSS
+  acquisitions, not an algorithm deadline.
+
+### Known limits
+- **One rule's encoding is a judgement call, and says so.** The CNSA 2.0 FAQ
+  answers the hybrid question twice with different force. The stronger reading
+  is encoded, marked `interpretation: contested` with `alt_reading: silent`,
+  and any conflict it drives prints both outcomes. The uncontested half of
+  NSA's position is a separate rule so the matrix keeps an anchor.
+- The `sbom-tools` adapter's payload shape is inferred from their Rust struct
+  definitions, not captured from a run. Its fixture is labelled constructed.
+- cdxgen is unverified as a CBOM producer; a code search of their repository
+  finds no `cryptoProperties` handling.
+- `security_level` selectors always evaluate to INDETERMINATE — there is no
+  config field for them yet.

cbomctl-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

cbomctl-0.1.0/PKG-INFO

@@ -0,0 +1,164 @@
+Metadata-Version: 2.5
+Name: cbomctl
+Version: 0.1.0
+Summary: Evaluate a CycloneDX CBOM against multiple national post-quantum policies and report where their verdicts contradict.
+Project-URL: Homepage, https://github.com/lvlrSajjad/cbomctl
+Project-URL: Issues, https://github.com/lvlrSajjad/cbomctl/issues
+Author: Sadjad Asadi
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: cbom,compliance,cyclonedx,post-quantum,pqc,sbom
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Topic :: Security :: Cryptography
+Requires-Python: >=3.11
+Requires-Dist: pydantic>=2.7
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: typer>=0.12
+Provides-Extra: llm
+Requires-Dist: anthropic>=0.40; extra == 'llm'
+Provides-Extra: test
+Requires-Dist: jsonschema>=4.21; extra == 'test'
+Requires-Dist: pytest>=8.0; extra == 'test'
+Description-Content-Type: text/markdown
+
+# cbomctl
+
+**One CBOM. Every jurisdiction's verdict. And where they contradict.**
+
+Germany and France recommend hybrid post-quantum key exchange. Australia
+recommends against it. The NSA wants ML-KEM-1024, not the -768 the others
+accept. If you ship into more than one of those markets, those are not
+independent checkboxes — and no tool will show you the collision.
+
+`cbomctl` takes a CBOM from any generator, runs it against several national PQC
+policies at once, and reports the matrix and the conflicts.
+
+> ⚠️ **Pre-release.** All seven policy packs have now been read from their
+> primary sources — every rule cites a section or page. Still not compliance
+> advice: read the sources yourself before acting on a verdict.
+> from an unverified rule carries a visible banner naming the packs involved.
+> See [docs/policy-sources.md](docs/policy-sources.md). Not compliance advice.
+
+<!-- badges: PyPI, CI, license -->
+
+## What it looks like
+
+```bash
+$ cbomctl verdict app-cbom.json --jurisdictions bsi-de,anssi-fr,asd-au,cnsa-2.0
+
+ASSET                          bsi-de    anssi-fr  asd-au    cnsa-2.0
+X25519MLKEM768 (key-agree)     PASS      PASS      WARN      FAIL
+ECDH secp256r1 (key-agree)     FAIL      FAIL      FAIL      FAIL
+RSA-2048 (ambiguous)           INDET     INDET     INDET     INDET
+
+CONFLICTS (1)
+c1  X25519MLKEM768 — no single construction satisfies all four.
+    bsi-de, anssi-fr  hybrid recommended        (guideline_recommendation)
+    asd-au            hybrid not recommended    (guideline_recommendation)
+    cnsa-2.0          requires ML-KEM-1024      (agency_requirement, NSS only)
+    Closest satisfies-all: hybrid X25519 + ML-KEM-1024 — clears bsi-de,
+    anssi-fr and cnsa-2.0, at a documented cost under asd-au.
+```
+
+`WARN` rather than `FAIL` for ASD is deliberate: the ISM *recommends against*
+hybrids, it does not prohibit them. Reporting a guideline as a mandate is the
+most common error in this space, so every rule carries a `binding` field —
+`statute`, `executive_order`, `agency_requirement`, `certification_requirement`,
+or `guideline_recommendation` — and the verdict follows from it.
+
+`INDET` is the tool declining to guess. That CBOM records `primitive: pke` for
+the RSA key, which cannot distinguish key transport from signature — and the
+answer moves the finding between critical and medium. Rather than pick, it says
+what is missing and what would resolve it.
+
+## Related tools
+
+Most of what a PQC readiness tool does, other people already do — several of
+them well. Use them.
+
+| tool | what it does |
+|---|---|
+| [CBOMkit](https://github.com/cbomkit/cbomkit), [cbomscanner](https://cyclonedx.org/capabilities/cbom/), KeyLens, [pqc-scanner](https://github.com/rauleteee/pqc-scanner) | generate CBOMs from source |
+| [open-quantum-secure](https://github.com/jimbo111/open-quantum-secure) | scans source + live TLS/SSH, generates CBOM, quantum readiness score, `--data-lifetime-years` HNDL weighting, and **seven compliance frameworks** including BSI, ASD ISM and ANSSI |
+| [sbom-tools](https://github.com/sbom-tool/sbom-tools) | CycloneDX/SPDX ingestion, semantic CBOM diff, quality scoring, CNSA 2.0 and NIST IR 8547 validation, SARIF/OSCAL |
+| IBM Quantum Safe Migration Orchestrator, SandboxAQ AQtive Guard, O3 Security | commercial discovery, risk prioritization and migration planning |
+
+**`cbomctl` overlaps all of them, and only two things are actually its own:**
+
+1. **Conflict as a computed output.** `open-quantum-secure` runs multiple
+   frameworks at once and its README documents cross-framework divergence
+   directly — this is not a gap in the market, and anyone claiming otherwise
+   has not read it. What it emits is one report per framework, concatenated;
+   you find the disagreement by comparing them yourself. `cbomctl` emits the
+   matrix, a conflict object naming the disagreeing authorities and the reason,
+   and a computed satisfies-all target where one exists.
+2. **Evaluating a CBOM you did not generate.** The tools above evaluate their
+   own scan. If your CBOM came from a vendor, a procurement process, or a
+   different generator, `cbomctl` will read it.
+
+If you want a scanner, use `open-quantum-secure`. If you want diff and
+validation, use `sbom-tools`. If you have a CBOM and need to know which
+jurisdiction's answer to believe, that is this tool.
+
+## What it does not do
+
+- **It does not scan source code or probe endpoints.** Bring a CBOM.
+- **It does not guess.** In CBOMkit's published Keycloak CBOM, 8 of 22
+  algorithm components carry no usable purpose signal — more than a third.
+  Those are reported as unresolved, with the range they would span if guessed.
+- **It does not give compliance advice.** It reports what a rule set says, with
+  the primary source and verification date attached. Every rule today is
+  unverified.
+- **It does not treat guidance as law.** See `binding`, above.
+- **It does not know when a CRQC arrives.** 2035 is a planning assumption
+  matching the NIST/NSM-10 horizon, not a prediction. `--crqc-year` changes it;
+  whatever you choose is stamped into the output.
+- **It does not diff SBOMs, verify signatures, or scan binaries.**
+
+## Also included
+
+`cbomctl prioritize` ranks findings by Mosca's inequality using data lifetimes
+you supply, weighting harvest-now-decrypt-later exposure highest.
+`cbomctl plan` emits an ordered migration plan. Both are useful; neither is
+novel — see Related tools.
+
+## Policy packs
+
+The rule sets live in [`policy-packs/`](policy-packs/) as a standalone,
+semantically versioned artifact with its own schema and changelog, so another
+tool can consume them without `cbomctl`. Every rule carries a primary-source
+URL, a `last_verified` date, a `binding` classification, and a `hybrid` stance.
+
+| pack | state |
+|---|---|
+| pack | state |
+|---|---|
+| pack | state |
+|---|---|
+| `bsi-de` | ✅ TR-02102-1 v2026-01 §2.1, §5.3.4 |
+| `anssi-fr` | ✅ 5/6 — ANSSI 2023 follow-up §1.1, §1.2, §2, §3.2, §4 |
+| `asd-au` | ✅ ISM Guidelines for Cryptography, 2026-09-03 |
+| `eu-roadmap` | ✅ Coordinated Implementation Roadmap Part 1 v1.1 |
+| `us-eo14412` | ✅ 91 FR 38483 §4(b), §5(c) |
+| `nist-ir8547` | ✅ **as a draft** — IR 8547 ipd Tables 2 and 4 |
+| `cnsa-2.0` | ✅ CNSA 2.0 FAQ v2.1 (Dec 2024), pp. 2, 6, 8, 19–20 |
+
+## Install
+
+```bash
+pip install cbomctl
+```
+
+Optional: `pip install cbomctl[llm]` adds a prose migration narrative that
+cannot affect any verdict.
+
+## Documentation
+
+[Design](docs/DESIGN.md) · [Policy sources and open questions](docs/policy-sources.md) ·
+[Policy packs](policy-packs/README.md)
+
+## License
+
+Apache-2.0

cbomctl-0.1.0/README.md

@@ -0,0 +1,139 @@
+# cbomctl
+
+**One CBOM. Every jurisdiction's verdict. And where they contradict.**
+
+Germany and France recommend hybrid post-quantum key exchange. Australia
+recommends against it. The NSA wants ML-KEM-1024, not the -768 the others
+accept. If you ship into more than one of those markets, those are not
+independent checkboxes — and no tool will show you the collision.
+
+`cbomctl` takes a CBOM from any generator, runs it against several national PQC
+policies at once, and reports the matrix and the conflicts.
+
+> ⚠️ **Pre-release.** All seven policy packs have now been read from their
+> primary sources — every rule cites a section or page. Still not compliance
+> advice: read the sources yourself before acting on a verdict.
+> from an unverified rule carries a visible banner naming the packs involved.
+> See [docs/policy-sources.md](docs/policy-sources.md). Not compliance advice.
+
+<!-- badges: PyPI, CI, license -->
+
+## What it looks like
+
+```bash
+$ cbomctl verdict app-cbom.json --jurisdictions bsi-de,anssi-fr,asd-au,cnsa-2.0
+
+ASSET                          bsi-de    anssi-fr  asd-au    cnsa-2.0
+X25519MLKEM768 (key-agree)     PASS      PASS      WARN      FAIL
+ECDH secp256r1 (key-agree)     FAIL      FAIL      FAIL      FAIL
+RSA-2048 (ambiguous)           INDET     INDET     INDET     INDET
+
+CONFLICTS (1)
+c1  X25519MLKEM768 — no single construction satisfies all four.
+    bsi-de, anssi-fr  hybrid recommended        (guideline_recommendation)
+    asd-au            hybrid not recommended    (guideline_recommendation)
+    cnsa-2.0          requires ML-KEM-1024      (agency_requirement, NSS only)
+    Closest satisfies-all: hybrid X25519 + ML-KEM-1024 — clears bsi-de,
+    anssi-fr and cnsa-2.0, at a documented cost under asd-au.
+```
+
+`WARN` rather than `FAIL` for ASD is deliberate: the ISM *recommends against*
+hybrids, it does not prohibit them. Reporting a guideline as a mandate is the
+most common error in this space, so every rule carries a `binding` field —
+`statute`, `executive_order`, `agency_requirement`, `certification_requirement`,
+or `guideline_recommendation` — and the verdict follows from it.
+
+`INDET` is the tool declining to guess. That CBOM records `primitive: pke` for
+the RSA key, which cannot distinguish key transport from signature — and the
+answer moves the finding between critical and medium. Rather than pick, it says
+what is missing and what would resolve it.
+
+## Related tools
+
+Most of what a PQC readiness tool does, other people already do — several of
+them well. Use them.
+
+| tool | what it does |
+|---|---|
+| [CBOMkit](https://github.com/cbomkit/cbomkit), [cbomscanner](https://cyclonedx.org/capabilities/cbom/), KeyLens, [pqc-scanner](https://github.com/rauleteee/pqc-scanner) | generate CBOMs from source |
+| [open-quantum-secure](https://github.com/jimbo111/open-quantum-secure) | scans source + live TLS/SSH, generates CBOM, quantum readiness score, `--data-lifetime-years` HNDL weighting, and **seven compliance frameworks** including BSI, ASD ISM and ANSSI |
+| [sbom-tools](https://github.com/sbom-tool/sbom-tools) | CycloneDX/SPDX ingestion, semantic CBOM diff, quality scoring, CNSA 2.0 and NIST IR 8547 validation, SARIF/OSCAL |
+| IBM Quantum Safe Migration Orchestrator, SandboxAQ AQtive Guard, O3 Security | commercial discovery, risk prioritization and migration planning |
+
+**`cbomctl` overlaps all of them, and only two things are actually its own:**
+
+1. **Conflict as a computed output.** `open-quantum-secure` runs multiple
+   frameworks at once and its README documents cross-framework divergence
+   directly — this is not a gap in the market, and anyone claiming otherwise
+   has not read it. What it emits is one report per framework, concatenated;
+   you find the disagreement by comparing them yourself. `cbomctl` emits the
+   matrix, a conflict object naming the disagreeing authorities and the reason,
+   and a computed satisfies-all target where one exists.
+2. **Evaluating a CBOM you did not generate.** The tools above evaluate their
+   own scan. If your CBOM came from a vendor, a procurement process, or a
+   different generator, `cbomctl` will read it.
+
+If you want a scanner, use `open-quantum-secure`. If you want diff and
+validation, use `sbom-tools`. If you have a CBOM and need to know which
+jurisdiction's answer to believe, that is this tool.
+
+## What it does not do
+
+- **It does not scan source code or probe endpoints.** Bring a CBOM.
+- **It does not guess.** In CBOMkit's published Keycloak CBOM, 8 of 22
+  algorithm components carry no usable purpose signal — more than a third.
+  Those are reported as unresolved, with the range they would span if guessed.
+- **It does not give compliance advice.** It reports what a rule set says, with
+  the primary source and verification date attached. Every rule today is
+  unverified.
+- **It does not treat guidance as law.** See `binding`, above.
+- **It does not know when a CRQC arrives.** 2035 is a planning assumption
+  matching the NIST/NSM-10 horizon, not a prediction. `--crqc-year` changes it;
+  whatever you choose is stamped into the output.
+- **It does not diff SBOMs, verify signatures, or scan binaries.**
+
+## Also included
+
+`cbomctl prioritize` ranks findings by Mosca's inequality using data lifetimes
+you supply, weighting harvest-now-decrypt-later exposure highest.
+`cbomctl plan` emits an ordered migration plan. Both are useful; neither is
+novel — see Related tools.
+
+## Policy packs
+
+The rule sets live in [`policy-packs/`](policy-packs/) as a standalone,
+semantically versioned artifact with its own schema and changelog, so another
+tool can consume them without `cbomctl`. Every rule carries a primary-source
+URL, a `last_verified` date, a `binding` classification, and a `hybrid` stance.
+
+| pack | state |
+|---|---|
+| pack | state |
+|---|---|
+| pack | state |
+|---|---|
+| `bsi-de` | ✅ TR-02102-1 v2026-01 §2.1, §5.3.4 |
+| `anssi-fr` | ✅ 5/6 — ANSSI 2023 follow-up §1.1, §1.2, §2, §3.2, §4 |
+| `asd-au` | ✅ ISM Guidelines for Cryptography, 2026-09-03 |
+| `eu-roadmap` | ✅ Coordinated Implementation Roadmap Part 1 v1.1 |
+| `us-eo14412` | ✅ 91 FR 38483 §4(b), §5(c) |
+| `nist-ir8547` | ✅ **as a draft** — IR 8547 ipd Tables 2 and 4 |
+| `cnsa-2.0` | ✅ CNSA 2.0 FAQ v2.1 (Dec 2024), pp. 2, 6, 8, 19–20 |
+
+## Install
+
+```bash
+pip install cbomctl
+```
+
+Optional: `pip install cbomctl[llm]` adds a prose migration narrative that
+cannot affect any verdict.
+
+## Documentation
+
+[Design](docs/DESIGN.md) · [Policy sources and open questions](docs/policy-sources.md) ·
+[Policy packs](policy-packs/README.md)
+
+## License
+
+Apache-2.0