quantbom 0.6.0__tar.gz

quantbom-0.6.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.

quantbom-0.6.0/PKG-INFO

@@ -0,0 +1,207 @@
+Metadata-Version: 2.4
+Name: quantbom
+Version: 0.6.0
+Summary: QuantBOM SDK — certify quantum software releases from your Qrisp/Qiskit pipeline (a SecQDevOps MOD-08 service).
+Author: SecQDevOps / QuantBOM
+License: Apache-2.0
+Project-URL: Homepage, https://certify.zortenet.eu
+Keywords: quantum,qiskit,qrisp,compliance,certification,cra,qbom,sbom
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Security
+Classifier: Topic :: Scientific/Engineering
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: quantum
+Requires-Dist: qiskit<3,>=2.0; extra == "quantum"
+Requires-Dist: qiskit-qasm3-import>=0.5; extra == "quantum"
+Provides-Extra: qrisp
+Requires-Dist: qrisp<1,>=0.8; extra == "qrisp"
+Provides-Extra: cirq
+Requires-Dist: cirq-core<2,>=1.4; extra == "cirq"
+Provides-Extra: braket
+Requires-Dist: amazon-braket-sdk<2,>=1.80; extra == "braket"
+Provides-Extra: pennylane
+Requires-Dist: pennylane<1,>=0.41; extra == "pennylane"
+Provides-Extra: cudaq
+Requires-Dist: cudaq<1,>=0.9; extra == "cudaq"
+Provides-Extra: ibm
+Requires-Dist: qiskit-ibm-runtime>=0.20; extra == "ibm"
+Provides-Extra: verify
+Requires-Dist: mqt.qcec>=3.10; extra == "verify"
+Provides-Extra: signing
+Requires-Dist: cryptography>=42; extra == "signing"
+Provides-Extra: sim
+Requires-Dist: qiskit-aer>=0.15; extra == "sim"
+Provides-Extra: qir
+Requires-Dist: qdk<2,>=1.30; extra == "qir"
+Requires-Dist: pyqir<1,>=0.10; extra == "qir"
+Requires-Dist: qirrunner<1,>=0.9; extra == "qir"
+Dynamic: license-file
+
+# QuantBOM SDK
+
+Certify a quantum software release straight from your **Qrisp / Qiskit / Cirq / Braket / PennyLane** pipeline.
+Evidence is collected locally (your source never leaves the machine) and sent to
+the QuantBOM service, which returns a signed, independently-verifiable CRA
+certificate — also mirrored to `./.quantbom/<release>/`.
+
+QuantBOM is a [SecQDevOps](https://certify.zortenet.eu) MOD-08 service.
+
+## Install
+
+```bash
+pip install "quantbom[quantum]"     # Qiskit + OpenQASM3 evidence collection
+# pip install "quantbom[quantum,qrisp]"   # also collect from Qrisp circuits
+# pip install "quantbom[quantum,cirq]"    # Cirq   — likewise [braket], [pennylane], [cudaq] (Linux only)
+# pip install "quantbom[quantum,ibm]"     # real IBM Runtime execution evidence
+# pip install "quantbom[quantum,qir]"     # also emit QIR (QDK) and check it against the program (QNT-07)
+# pip install "quantbom[signing]"         # sign your evidence (quantbom keygen / --sign) and verify certificates offline
+# Each frontend extra pins the version range the conformance suite holds for
+# (harness_manifest.json `requires`); `quantbom actions --framework <name>` shows
+# the recorded run, or that conformance is still pending.
+```
+
+The core install is a lightweight, stdlib-only client; the `quantum` extra adds
+the toolchain needed to build the evidence (QBOM).
+
+## Use
+
+Set your API key (generate it in the QuantBOM dashboard):
+
+```bash
+export QUANTBOM_API_KEY=qb_live_...
+export QUANTBOM_API_URL=https://certify.zortenet.eu   # default
+```
+
+**Post-run call**
+
+```python
+import quantbom
+result = quantbom.certify(my_circuit, release="portfolio-opt@1.2.3")
+print(result["overall_status"], result["certificate"]["certificate_id"])
+```
+
+**Decorator** — certifies the circuit a function returns:
+
+```python
+@quantbom.certified(release="vqe@2.1")
+def build(): ...   # returns a qiskit/qrisp circuit
+```
+
+**Qiskit primitive wrapper** — certify transparently on `.run()`:
+
+```python
+sampler = quantbom.wrap(SamplerV2(mode=backend), release="vqe@2.1")
+job = sampler.run([circuit])   # certifies, then runs as normal
+```
+
+**Sign your evidence** — the certificate's authorship claim (CRA-SIGN-01)
+rests on *your* signature, not the service's. One key per organisation:
+
+```bash
+pip install "quantbom[signing]"
+quantbom keygen                                   # ~/.quantbom/signing.key (0600) + signing.pub — back it up
+quantbom certify --qpy circuit.qpy --release my-app@1.0 --sign
+```
+
+In Python: `quantbom.certify(circuit, release=..., sign=True)`. The SDK signs
+the collected evidence (Ed25519, in-toto/DSSE) before upload; the service
+verifies it, countersigns what it received, and the certificate names both
+key ids. Without `--sign` the release is **NON_COMPLIANT**: CRA-SIGN-01 rests
+on the producer's signature, the service's countersignature is a receipt and
+never substitutes, and the certificate says in words that the producer did
+not sign. `--key FILE` or `QUANTBOM_SIGNING_KEY` point at a key elsewhere; in
+CI, store the key as a secret and pass it to the `quantbom-certify` action's
+`signing-key` input.
+
+**Verify a certificate without trusting us** — for the auditor, the customer,
+or your future self. Needs only the wheel, never the service code:
+
+```bash
+pip install "quantbom[signing]"
+quantbom keys --pin                        # fetch the service's signing keys once; pin them
+quantbom verify .quantbom/my-app@1.0        # the mirror, a collect bundle, or a zip of either
+```
+
+It re-hashes every artifact against the QBOM, verifies the producer's
+attestation and the service's receipt, recomputes the CSNAP's and the
+certificate's reproducibility hashes and bindings, and checks the certificate
+signature against a key that is *anchored* (pinned from `/v1/keys`, or given
+with `--keys` / `--service-key`). What it does not do, it says: the 24
+controls are not re-run (that needs the gate, `verify_bundle.py` in the
+repository). Verdicts: `VERIFIED` (exit 0), `FAILED`, or `UNANCHORED` when
+every check passed but nothing was pinned.
+
+**CLI / CI**
+
+```bash
+quantbom certify --qpy circuit.qpy --release my-app@1.0 --mode gate --sign
+quantbom certify --qasm3 program.qasm3 --release my-app@1.0
+quantbom certify --demo --release smoke-test     # needs the [qrisp] extra
+
+# any supported framework, straight from your code (module:attr or file.py:attr;
+# a function is called, an object such as a PennyLane QNode is passed as is)
+quantbom certify --entry my_pkg.circuits:build --release my-app@1.0 --expect 10=1.0
+```
+
+`--mode gate` exits non-zero on a non-compliant release (use it to fail CI);
+`--mode report` (default) never fails your pipeline. `--expect` outcomes are
+read in your framework's own bit order (`--expected-order qiskit` to override).
+For Qrisp that depends on what you hand over: a `QuantumCircuit` reads like
+`run()` (qubit 0 rightmost), a `QuantumSession` like `get_measurement()` and a
+Jasp program like `measure()` (qubit 0 leftmost) — declare what Qrisp shows you.
+
+**Adding evidence from other modules** — collect, add, then certify the bundle:
+
+```bash
+quantbom collect --entry my_pkg.circuits:build --release my-app@1.0 --out bundle/
+quantbom attest tests         --bundle bundle/ --suite quantum-security-suite --outcome passed --passed 42
+quantbom attest vulns         --bundle bundle/ --policy-url https://example.org/security --contact mailto:security@example.org
+quantbom attest constant-time --bundle bundle/ --tool dudect --target kyber_decaps --measurements timings.csv
+quantbom attest crypto        --bundle bundle/ --cbom cbom.cdx.json
+quantbom sign --bundle bundle/                    # last, so the signature covers it all
+quantbom certify --bundle bundle/ --release my-app@1.0
+```
+
+The four `attest` commands are the partner-module evidence the gate otherwise
+reports as N-A: a MOD-05 security test report (`MOD05-TEST-01`), a VEX/VDR and
+a coordinated-disclosure policy (`CRA-VULN-01`, `CRA-VDP-01`), a constant-time
+proof from dudect / ctgrind / Binsec-Rel (`CRA-ESR-06`), and a CBOM
+PQC-readiness assessment (`CRA-CRYPTO-01`). Each writes a hash-bound document
+into the bundle; the same bytes the repository scripts write.
+
+In Python: `quantbom.collect(...)`, then `quantbom.attest.tests(bundle, ...)`,
+`.vulnerability_handling(...)`, `.constant_time(...)`, `.crypto(...)`, then
+`quantbom.certify(bundle="bundle", release=..., sign=True)`.
+
+**What can the harness do for me?**
+
+```bash
+quantbom actions --framework cirq          # every action, its status for Cirq, how to turn it on
+quantbom actions --requirement CRA-II-3    # which actions produce evidence for this requirement
+```
+
+Answered offline from the index shipped in the package — the same answer the
+service gives at `GET /v1/harness`.
+
+## Behaviour
+
+- **Non-intrusive & fail-soft.** If the service is unreachable or credits are
+  exhausted, a warning is logged and your quantum run continues. Certifying is
+  additive (unless you opt into `gate` mode).
+- **Privacy by design.** Only the QBOM/evidence (hashes, metrics, backend
+  binding) is uploaded — not your program source.
+- **Local mirror.** Every result is written to `./.quantbom/<release>/`
+  (the QBOM as the gate ran on it, CSNAP, certificate, attestation, the
+  service's receipt and public keys, verification) so you keep your own
+  audit bundle and can re-verify it offline with `quantbom verify`.
+
+| Env var | Purpose |
+|---|---|
+| `QUANTBOM_API_KEY` | your API key (required for actions) |
+| `QUANTBOM_API_URL` | service base URL (default `https://certify.zortenet.eu`) |
+| `QUANTBOM_SIGNING_KEY` | producer signing key for `--sign` (default `~/.quantbom/signing.key`) |

quantbom-0.6.0/README.md

@@ -0,0 +1,163 @@
+# QuantBOM SDK
+
+Certify a quantum software release straight from your **Qrisp / Qiskit / Cirq / Braket / PennyLane** pipeline.
+Evidence is collected locally (your source never leaves the machine) and sent to
+the QuantBOM service, which returns a signed, independently-verifiable CRA
+certificate — also mirrored to `./.quantbom/<release>/`.
+
+QuantBOM is a [SecQDevOps](https://certify.zortenet.eu) MOD-08 service.
+
+## Install
+
+```bash
+pip install "quantbom[quantum]"     # Qiskit + OpenQASM3 evidence collection
+# pip install "quantbom[quantum,qrisp]"   # also collect from Qrisp circuits
+# pip install "quantbom[quantum,cirq]"    # Cirq   — likewise [braket], [pennylane], [cudaq] (Linux only)
+# pip install "quantbom[quantum,ibm]"     # real IBM Runtime execution evidence
+# pip install "quantbom[quantum,qir]"     # also emit QIR (QDK) and check it against the program (QNT-07)
+# pip install "quantbom[signing]"         # sign your evidence (quantbom keygen / --sign) and verify certificates offline
+# Each frontend extra pins the version range the conformance suite holds for
+# (harness_manifest.json `requires`); `quantbom actions --framework <name>` shows
+# the recorded run, or that conformance is still pending.
+```
+
+The core install is a lightweight, stdlib-only client; the `quantum` extra adds
+the toolchain needed to build the evidence (QBOM).
+
+## Use
+
+Set your API key (generate it in the QuantBOM dashboard):
+
+```bash
+export QUANTBOM_API_KEY=qb_live_...
+export QUANTBOM_API_URL=https://certify.zortenet.eu   # default
+```
+
+**Post-run call**
+
+```python
+import quantbom
+result = quantbom.certify(my_circuit, release="portfolio-opt@1.2.3")
+print(result["overall_status"], result["certificate"]["certificate_id"])
+```
+
+**Decorator** — certifies the circuit a function returns:
+
+```python
+@quantbom.certified(release="vqe@2.1")
+def build(): ...   # returns a qiskit/qrisp circuit
+```
+
+**Qiskit primitive wrapper** — certify transparently on `.run()`:
+
+```python
+sampler = quantbom.wrap(SamplerV2(mode=backend), release="vqe@2.1")
+job = sampler.run([circuit])   # certifies, then runs as normal
+```
+
+**Sign your evidence** — the certificate's authorship claim (CRA-SIGN-01)
+rests on *your* signature, not the service's. One key per organisation:
+
+```bash
+pip install "quantbom[signing]"
+quantbom keygen                                   # ~/.quantbom/signing.key (0600) + signing.pub — back it up
+quantbom certify --qpy circuit.qpy --release my-app@1.0 --sign
+```
+
+In Python: `quantbom.certify(circuit, release=..., sign=True)`. The SDK signs
+the collected evidence (Ed25519, in-toto/DSSE) before upload; the service
+verifies it, countersigns what it received, and the certificate names both
+key ids. Without `--sign` the release is **NON_COMPLIANT**: CRA-SIGN-01 rests
+on the producer's signature, the service's countersignature is a receipt and
+never substitutes, and the certificate says in words that the producer did
+not sign. `--key FILE` or `QUANTBOM_SIGNING_KEY` point at a key elsewhere; in
+CI, store the key as a secret and pass it to the `quantbom-certify` action's
+`signing-key` input.
+
+**Verify a certificate without trusting us** — for the auditor, the customer,
+or your future self. Needs only the wheel, never the service code:
+
+```bash
+pip install "quantbom[signing]"
+quantbom keys --pin                        # fetch the service's signing keys once; pin them
+quantbom verify .quantbom/my-app@1.0        # the mirror, a collect bundle, or a zip of either
+```
+
+It re-hashes every artifact against the QBOM, verifies the producer's
+attestation and the service's receipt, recomputes the CSNAP's and the
+certificate's reproducibility hashes and bindings, and checks the certificate
+signature against a key that is *anchored* (pinned from `/v1/keys`, or given
+with `--keys` / `--service-key`). What it does not do, it says: the 24
+controls are not re-run (that needs the gate, `verify_bundle.py` in the
+repository). Verdicts: `VERIFIED` (exit 0), `FAILED`, or `UNANCHORED` when
+every check passed but nothing was pinned.
+
+**CLI / CI**
+
+```bash
+quantbom certify --qpy circuit.qpy --release my-app@1.0 --mode gate --sign
+quantbom certify --qasm3 program.qasm3 --release my-app@1.0
+quantbom certify --demo --release smoke-test     # needs the [qrisp] extra
+
+# any supported framework, straight from your code (module:attr or file.py:attr;
+# a function is called, an object such as a PennyLane QNode is passed as is)
+quantbom certify --entry my_pkg.circuits:build --release my-app@1.0 --expect 10=1.0
+```
+
+`--mode gate` exits non-zero on a non-compliant release (use it to fail CI);
+`--mode report` (default) never fails your pipeline. `--expect` outcomes are
+read in your framework's own bit order (`--expected-order qiskit` to override).
+For Qrisp that depends on what you hand over: a `QuantumCircuit` reads like
+`run()` (qubit 0 rightmost), a `QuantumSession` like `get_measurement()` and a
+Jasp program like `measure()` (qubit 0 leftmost) — declare what Qrisp shows you.
+
+**Adding evidence from other modules** — collect, add, then certify the bundle:
+
+```bash
+quantbom collect --entry my_pkg.circuits:build --release my-app@1.0 --out bundle/
+quantbom attest tests         --bundle bundle/ --suite quantum-security-suite --outcome passed --passed 42
+quantbom attest vulns         --bundle bundle/ --policy-url https://example.org/security --contact mailto:security@example.org
+quantbom attest constant-time --bundle bundle/ --tool dudect --target kyber_decaps --measurements timings.csv
+quantbom attest crypto        --bundle bundle/ --cbom cbom.cdx.json
+quantbom sign --bundle bundle/                    # last, so the signature covers it all
+quantbom certify --bundle bundle/ --release my-app@1.0
+```
+
+The four `attest` commands are the partner-module evidence the gate otherwise
+reports as N-A: a MOD-05 security test report (`MOD05-TEST-01`), a VEX/VDR and
+a coordinated-disclosure policy (`CRA-VULN-01`, `CRA-VDP-01`), a constant-time
+proof from dudect / ctgrind / Binsec-Rel (`CRA-ESR-06`), and a CBOM
+PQC-readiness assessment (`CRA-CRYPTO-01`). Each writes a hash-bound document
+into the bundle; the same bytes the repository scripts write.
+
+In Python: `quantbom.collect(...)`, then `quantbom.attest.tests(bundle, ...)`,
+`.vulnerability_handling(...)`, `.constant_time(...)`, `.crypto(...)`, then
+`quantbom.certify(bundle="bundle", release=..., sign=True)`.
+
+**What can the harness do for me?**
+
+```bash
+quantbom actions --framework cirq          # every action, its status for Cirq, how to turn it on
+quantbom actions --requirement CRA-II-3    # which actions produce evidence for this requirement
+```
+
+Answered offline from the index shipped in the package — the same answer the
+service gives at `GET /v1/harness`.
+
+## Behaviour
+
+- **Non-intrusive & fail-soft.** If the service is unreachable or credits are
+  exhausted, a warning is logged and your quantum run continues. Certifying is
+  additive (unless you opt into `gate` mode).
+- **Privacy by design.** Only the QBOM/evidence (hashes, metrics, backend
+  binding) is uploaded — not your program source.
+- **Local mirror.** Every result is written to `./.quantbom/<release>/`
+  (the QBOM as the gate ran on it, CSNAP, certificate, attestation, the
+  service's receipt and public keys, verification) so you keep your own
+  audit bundle and can re-verify it offline with `quantbom verify`.
+
+| Env var | Purpose |
+|---|---|
+| `QUANTBOM_API_KEY` | your API key (required for actions) |
+| `QUANTBOM_API_URL` | service base URL (default `https://certify.zortenet.eu`) |
+| `QUANTBOM_SIGNING_KEY` | producer signing key for `--sign` (default `~/.quantbom/signing.key`) |

quantbom-0.6.0/pyproject.toml

@@ -0,0 +1,59 @@
+[build-system]
+requires = ["setuptools>=69"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "quantbom"
+version = "0.6.0"
+description = "QuantBOM SDK — certify quantum software releases from your Qrisp/Qiskit pipeline (a SecQDevOps MOD-08 service)."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "Apache-2.0" }
+authors = [{ name = "SecQDevOps / QuantBOM" }]
+keywords = ["quantum", "qiskit", "qrisp", "compliance", "certification", "cra", "qbom", "sbom"]
+classifiers = [
+  "Development Status :: 4 - Beta",
+  "Intended Audience :: Developers",
+  "License :: OSI Approved :: Apache Software License",
+  "Programming Language :: Python :: 3",
+  "Topic :: Security",
+  "Topic :: Scientific/Engineering",
+]
+# Core install is a lightweight, stdlib-only HTTP client. Evidence collection
+# needs the quantum toolchain — opt in with the extras below.
+dependencies = []
+
+[project.optional-dependencies]
+quantum = ["qiskit>=2.0,<3", "qiskit-qasm3-import>=0.5"]
+qrisp = ["qrisp>=0.8,<1"]
+# other frontends (one extra per adapter; the ranges are the ones the
+# conformance suite holds for — harness_manifest.json `requires` must agree)
+cirq = ["cirq-core>=1.4,<2"]
+braket = ["amazon-braket-sdk>=1.80,<2"]
+pennylane = ["pennylane>=0.41,<1"]
+cudaq = ["cudaq>=0.9,<1"]
+ibm = ["qiskit-ibm-runtime>=0.20"]
+# >=3.10: earlier releases DECIDE circuits that 3.10+ refuses (a measurement deferred past a
+# gate on the measured qubit — tests/harness/test_k0b.py B1); one circuit must get one verdict
+# everywhere, so the floor is the version whose refusal is the honest answer
+verify = ["mqt.qcec>=3.10"]
+# producer signing from a pip install: `quantbom keygen` / `quantbom sign` / `certify --sign`
+signing = ["cryptography>=42"]
+# local execution of dynamic circuits, and the noise of the synthetic `generic` backend
+sim = ["qiskit-aer>=0.15"]
+# QIR as the second standards-named IR (K5): the QDK compiles the OpenQASM 3 export,
+# pyqir inspects the module, qirrunner executes it for the consistency check (QNT-07)
+qir = ["qdk>=1.30,<2", "pyqir>=0.10,<1", "qirrunner>=0.9,<1"]
+
+[project.scripts]
+quantbom = "quantbom.cli:main"
+
+[project.urls]
+Homepage = "https://certify.zortenet.eu"
+
+[tool.setuptools]
+packages = ["quantbom", "quantbom.frameworks", "quantbom.actions"]
+license-files = ["LICENSE"]
+
+[tool.setuptools.package-data]
+quantbom = ["harness.json"]