qcheck-quantum 0.2.0__tar.gz

qcheck_quantum-0.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2026 qcheck contributors
+
+   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.

qcheck_quantum-0.2.0/NOTICE

@@ -0,0 +1,8 @@
+qcheck
+Copyright 2026 qcheck contributors
+
+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

qcheck_quantum-0.2.0/PKG-INFO

@@ -0,0 +1,226 @@
+Metadata-Version: 2.4
+Name: qcheck-quantum
+Version: 0.2.0
+Summary: Verify LLM-generated quantum code (Qiskit / OpenQASM) statically and safely.
+Author: qcheck contributors
+Maintainer-email: JCQuankey <dev@quankey.xyz>
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/JCQuankey/qcheck
+Project-URL: Repository, https://github.com/JCQuankey/qcheck
+Project-URL: Issues, https://github.com/JCQuankey/qcheck/issues
+Keywords: quantum,qiskit,openqasm,llm,linter,code-review,static-analysis,sarif
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Scientific/Engineering :: Physics
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == "dev"
+Provides-Extra: release
+Requires-Dist: build>=1; extra == "release"
+Requires-Dist: twine>=5; extra == "release"
+Dynamic: license-file
+
+# qcheck
+
+**AI writes quantum code. qcheck reviews it.**
+
+`qcheck` is a lightweight review layer for AI-generated Qiskit and OpenQASM
+snippets. It catches common issues early - removed-in-1.0 APIs, unsafe patterns,
+missing measurements, parse errors - so agents and developers can improve quantum
+code before it reaches humans, CI, or simulators. Tiny, dependency-free, and it
+reviews code without ever executing it.
+
+Why it matters: LLMs write quantum code that fails to run **40-70% of the time**
+one-shot (QuanBench+ 2026: Qiskit 59.5% / PennyLane 42.9% pass; QCoder 2026: ~70%
+one-shot failure). qcheck catches the avoidable share of that early.
+
+```bash
+qcheck verify circuit.qasm
+qcheck verify snippet.py --json
+```
+
+## Why this exists
+
+An LLM agent (or a developer pasting from a chat assistant) produces a Qiskit/QASM snippet.
+Will it run? Is it using an API that was removed in Qiskit 1.0? Does it measure?
+Is it even safe to touch? Today you find out by running it - wasting time, and
+in an agent loop, running untrusted model output. `qcheck` answers in
+milliseconds, statically.
+
+## Install
+
+```bash
+# From source (works today)
+git clone https://github.com/JCQuankey/qcheck && cd qcheck
+pip install -e ".[dev]"     # editable install + pytest
+```
+
+Once the first release is published, install from PyPI:
+
+```bash
+pip install qcheck-quantum   # available after the first PyPI release
+```
+
+The PyPI **distribution** name is `qcheck-quantum` (the bare `qcheck` name is
+taken on PyPI); the installed **command** and the import package are both
+`qcheck`. v0 has **zero runtime dependencies** (standard library only). Release
+process: [`docs/RELEASING.md`](https://github.com/JCQuankey/qcheck/blob/main/docs/RELEASING.md).
+
+## Quickstart
+
+```bash
+qcheck verify examples/broken_qiskit_execute.py   # one file
+qcheck verify examples/                            # a whole directory (recursive)
+qcheck verify a.py b.qasm circuits/                # several paths at once
+cat snippet.py | qcheck verify -                   # stdin (for agents)
+```
+
+Example output:
+
+```
+qcheck 0.2.0  [FAIL]  examples/broken_qiskit_execute.py  (qiskit)
+  [error] QISKIT-REMOVED-IMPORT: 'from qiskit import execute' was removed in Qiskit 1.0
+  [warning] QISKIT-DEPRECATED-GATE: QuantumCircuit.cnot() is deprecated; use .cx().
+  fix -> Replace execute() with a primitive (Sampler/Estimator) or backend.run().
+```
+
+Reviewing multiple files prints a per-file summary and exits with the worst
+result found (unsafe > failed > passed). Directory recursion skips virtualenvs,
+VCS, caches, and build output (`.venv`, `node_modules`, `.git`, `site-packages`,
+`build`, `dist`, ...) so it reviews your code, not your dependencies. To review a
+file inside one of those, pass it explicitly.
+
+## JSON output (for agents & CI)
+
+```bash
+qcheck verify snippet.py --json
+```
+
+For a single file, returns `{status, framework, syntax_valid, unsafe,
+static_checks, errors, warnings, suggested_fixes, confidence,
+runnable_in_simulator, qcheck_version}`. For multiple files or a directory,
+returns an envelope `{qcheck_version, results: [<per-file object + "path">...],
+summary: {files, passed, failed, unsafe, read_errors}}`. Designed to be parsed by
+an LLM agent that just generated the code, or by a CI gate. Exit codes: `0` pass,
+`1` verification failed, `2` unsafe/unsupported, `3` internal error.
+
+## Use it in CI (GitHub Action)
+
+qcheck ships a composite GitHub Action. In your repo's
+`.github/workflows/qcheck.yml`:
+
+```yaml
+- uses: actions/checkout@v4
+- uses: JCQuankey/qcheck@main
+  with:
+    paths: "."     # or a folder, e.g. "circuits/"
+```
+
+The step fails the job when qcheck finds errors or unsafe code. See
+[`examples/github-action.yml`](https://github.com/JCQuankey/qcheck/blob/main/examples/github-action.yml).
+
+## SARIF output (GitHub Code Scanning)
+
+qcheck can emit SARIF 2.1.0 so findings show up as **code scanning alerts** on
+the Security tab and inline on pull requests, instead of only in the log:
+
+```bash
+qcheck verify . --format sarif --output qcheck.sarif
+```
+
+In a workflow, generate the SARIF and let the caller upload it (upload needs
+`security-events: write`, best granted by the consuming repo):
+
+```yaml
+permissions:
+  contents: read
+  security-events: write
+steps:
+  - uses: actions/checkout@v4
+  - uses: JCQuankey/qcheck@main
+    with:
+      format: sarif
+      output: qcheck.sarif
+  - uses: github/codeql-action/upload-sarif@v3
+    with:
+      sarif_file: qcheck.sarif
+```
+
+SARIF reports static qcheck findings (rule id, level, file, line) - it does not
+prove quantum correctness. `stdin` input uses a synthetic `stdin` URI and is not
+meant for code-scanning upload.
+
+## What v0 checks
+
+**OpenQASM 2/3:** missing header, undeclared registers, index-out-of-range,
+malformed measurements, unsupported includes, suspicious non-QASM content.
+**Qiskit Python:** Python syntax, missing `QuantumCircuit` import, missing
+measurement, and Qiskit-1.0 breaking changes LLMs still emit (`execute()`,
+`from qiskit import Aer/execute`, deprecated gate aliases like `cnot`->`cx`).
+
+## Safety policy
+
+`qcheck` **never executes the input.** Qiskit snippets are analyzed with the
+Python `ast` module (parse, don't run). Any filesystem/network/process/dynamic-
+exec construct (`os`, `subprocess`, `eval`, `open`, ...) marks the snippet
+**unsafe** and exits `2`. QASM input is text-scanned. This is deliberate: an
+agent-facing verifier that *ran* untrusted model output would be a remote-code-
+execution vector (see Qiskit CVE-2025-2000 for the QPY/pickle precedent). See
+[`SECURITY.md`](https://github.com/JCQuankey/qcheck/blob/main/SECURITY.md) for the full threat model.
+
+## Scope
+
+qcheck v0 focuses on static review signals for Qiskit and OpenQASM: API usage
+(including Qiskit 1.0 removals), unsafe patterns, missing measurements, parse
+issues, and common LLM-generated mistakes. It reviews code without executing it,
+so it's safe to run on untrusted model output inside an agent loop or CI.
+
+It's a fast first-pass reviewer - pair it with your tests and simulators for the
+rest. For methodology and scope details, see the
+[leaderboard methodology](https://github.com/JCQuankey/qcheck/blob/main/leaderboard/methodology.md).
+
+## Roadmap
+
+- v0 (this): CLI, Qiskit + OpenQASM static checks, JSON, safety screen. **Zero runtime deps.**
+- v1: sandboxed simulation (opt-in), PennyLane + Cirq, LLM-powered fix suggestions, GitHub Action, MCP server (`verify_quantum_code`).
+- Public **static-check leaderboard** for LLM-generated quantum code (see `leaderboard/`) + anonymized error dataset.
+
+## Leaderboard
+
+qcheck includes a **static review benchmark** for AI-generated quantum code: it
+tracks how often model outputs pass qcheck's current review checks
+(`static_pass_rate`) on a small public Qiskit/OpenQASM task set - an early quality
+signal for agents and LLM workflows. The rows shown today are labelled **SAMPLE/demo**.
+
+- [`leaderboard/README.md`](https://github.com/JCQuankey/qcheck/blob/main/leaderboard/README.md) - how to add a submission and run it
+- [`leaderboard/methodology.md`](https://github.com/JCQuankey/qcheck/blob/main/leaderboard/methodology.md) - scope and methodology
+- [`leaderboard/site/leaderboard.md`](https://github.com/JCQuankey/qcheck/blob/main/leaderboard/site/leaderboard.md) - the generated table
+
+## Contributing
+
+Issues and PRs welcome - especially new failure fixtures (a real LLM-generated
+snippet that should fail but currently passes, or vice versa). Each fixture
+makes qcheck sharper and feeds the public error taxonomy.
+
+## Contact
+
+- Technical questions / maintainer contact: **dev@quankey.xyz**
+- Security issues: **security@quankey.xyz** (see [`SECURITY.md`](https://github.com/JCQuankey/qcheck/blob/main/SECURITY.md))
+
+Maintained by JCQuankey / qcheck contributors. qcheck runs locally, sends no
+telemetry, and reviews code without executing it.
+
+## License
+
+Apache-2.0.

qcheck_quantum-0.2.0/README.md

@@ -0,0 +1,193 @@
+# qcheck
+
+**AI writes quantum code. qcheck reviews it.**
+
+`qcheck` is a lightweight review layer for AI-generated Qiskit and OpenQASM
+snippets. It catches common issues early - removed-in-1.0 APIs, unsafe patterns,
+missing measurements, parse errors - so agents and developers can improve quantum
+code before it reaches humans, CI, or simulators. Tiny, dependency-free, and it
+reviews code without ever executing it.
+
+Why it matters: LLMs write quantum code that fails to run **40-70% of the time**
+one-shot (QuanBench+ 2026: Qiskit 59.5% / PennyLane 42.9% pass; QCoder 2026: ~70%
+one-shot failure). qcheck catches the avoidable share of that early.
+
+```bash
+qcheck verify circuit.qasm
+qcheck verify snippet.py --json
+```
+
+## Why this exists
+
+An LLM agent (or a developer pasting from a chat assistant) produces a Qiskit/QASM snippet.
+Will it run? Is it using an API that was removed in Qiskit 1.0? Does it measure?
+Is it even safe to touch? Today you find out by running it - wasting time, and
+in an agent loop, running untrusted model output. `qcheck` answers in
+milliseconds, statically.
+
+## Install
+
+```bash
+# From source (works today)
+git clone https://github.com/JCQuankey/qcheck && cd qcheck
+pip install -e ".[dev]"     # editable install + pytest
+```
+
+Once the first release is published, install from PyPI:
+
+```bash
+pip install qcheck-quantum   # available after the first PyPI release
+```
+
+The PyPI **distribution** name is `qcheck-quantum` (the bare `qcheck` name is
+taken on PyPI); the installed **command** and the import package are both
+`qcheck`. v0 has **zero runtime dependencies** (standard library only). Release
+process: [`docs/RELEASING.md`](https://github.com/JCQuankey/qcheck/blob/main/docs/RELEASING.md).
+
+## Quickstart
+
+```bash
+qcheck verify examples/broken_qiskit_execute.py   # one file
+qcheck verify examples/                            # a whole directory (recursive)
+qcheck verify a.py b.qasm circuits/                # several paths at once
+cat snippet.py | qcheck verify -                   # stdin (for agents)
+```
+
+Example output:
+
+```
+qcheck 0.2.0  [FAIL]  examples/broken_qiskit_execute.py  (qiskit)
+  [error] QISKIT-REMOVED-IMPORT: 'from qiskit import execute' was removed in Qiskit 1.0
+  [warning] QISKIT-DEPRECATED-GATE: QuantumCircuit.cnot() is deprecated; use .cx().
+  fix -> Replace execute() with a primitive (Sampler/Estimator) or backend.run().
+```
+
+Reviewing multiple files prints a per-file summary and exits with the worst
+result found (unsafe > failed > passed). Directory recursion skips virtualenvs,
+VCS, caches, and build output (`.venv`, `node_modules`, `.git`, `site-packages`,
+`build`, `dist`, ...) so it reviews your code, not your dependencies. To review a
+file inside one of those, pass it explicitly.
+
+## JSON output (for agents & CI)
+
+```bash
+qcheck verify snippet.py --json
+```
+
+For a single file, returns `{status, framework, syntax_valid, unsafe,
+static_checks, errors, warnings, suggested_fixes, confidence,
+runnable_in_simulator, qcheck_version}`. For multiple files or a directory,
+returns an envelope `{qcheck_version, results: [<per-file object + "path">...],
+summary: {files, passed, failed, unsafe, read_errors}}`. Designed to be parsed by
+an LLM agent that just generated the code, or by a CI gate. Exit codes: `0` pass,
+`1` verification failed, `2` unsafe/unsupported, `3` internal error.
+
+## Use it in CI (GitHub Action)
+
+qcheck ships a composite GitHub Action. In your repo's
+`.github/workflows/qcheck.yml`:
+
+```yaml
+- uses: actions/checkout@v4
+- uses: JCQuankey/qcheck@main
+  with:
+    paths: "."     # or a folder, e.g. "circuits/"
+```
+
+The step fails the job when qcheck finds errors or unsafe code. See
+[`examples/github-action.yml`](https://github.com/JCQuankey/qcheck/blob/main/examples/github-action.yml).
+
+## SARIF output (GitHub Code Scanning)
+
+qcheck can emit SARIF 2.1.0 so findings show up as **code scanning alerts** on
+the Security tab and inline on pull requests, instead of only in the log:
+
+```bash
+qcheck verify . --format sarif --output qcheck.sarif
+```
+
+In a workflow, generate the SARIF and let the caller upload it (upload needs
+`security-events: write`, best granted by the consuming repo):
+
+```yaml
+permissions:
+  contents: read
+  security-events: write
+steps:
+  - uses: actions/checkout@v4
+  - uses: JCQuankey/qcheck@main
+    with:
+      format: sarif
+      output: qcheck.sarif
+  - uses: github/codeql-action/upload-sarif@v3
+    with:
+      sarif_file: qcheck.sarif
+```
+
+SARIF reports static qcheck findings (rule id, level, file, line) - it does not
+prove quantum correctness. `stdin` input uses a synthetic `stdin` URI and is not
+meant for code-scanning upload.
+
+## What v0 checks
+
+**OpenQASM 2/3:** missing header, undeclared registers, index-out-of-range,
+malformed measurements, unsupported includes, suspicious non-QASM content.
+**Qiskit Python:** Python syntax, missing `QuantumCircuit` import, missing
+measurement, and Qiskit-1.0 breaking changes LLMs still emit (`execute()`,
+`from qiskit import Aer/execute`, deprecated gate aliases like `cnot`->`cx`).
+
+## Safety policy
+
+`qcheck` **never executes the input.** Qiskit snippets are analyzed with the
+Python `ast` module (parse, don't run). Any filesystem/network/process/dynamic-
+exec construct (`os`, `subprocess`, `eval`, `open`, ...) marks the snippet
+**unsafe** and exits `2`. QASM input is text-scanned. This is deliberate: an
+agent-facing verifier that *ran* untrusted model output would be a remote-code-
+execution vector (see Qiskit CVE-2025-2000 for the QPY/pickle precedent). See
+[`SECURITY.md`](https://github.com/JCQuankey/qcheck/blob/main/SECURITY.md) for the full threat model.
+
+## Scope
+
+qcheck v0 focuses on static review signals for Qiskit and OpenQASM: API usage
+(including Qiskit 1.0 removals), unsafe patterns, missing measurements, parse
+issues, and common LLM-generated mistakes. It reviews code without executing it,
+so it's safe to run on untrusted model output inside an agent loop or CI.
+
+It's a fast first-pass reviewer - pair it with your tests and simulators for the
+rest. For methodology and scope details, see the
+[leaderboard methodology](https://github.com/JCQuankey/qcheck/blob/main/leaderboard/methodology.md).
+
+## Roadmap
+
+- v0 (this): CLI, Qiskit + OpenQASM static checks, JSON, safety screen. **Zero runtime deps.**
+- v1: sandboxed simulation (opt-in), PennyLane + Cirq, LLM-powered fix suggestions, GitHub Action, MCP server (`verify_quantum_code`).
+- Public **static-check leaderboard** for LLM-generated quantum code (see `leaderboard/`) + anonymized error dataset.
+
+## Leaderboard
+
+qcheck includes a **static review benchmark** for AI-generated quantum code: it
+tracks how often model outputs pass qcheck's current review checks
+(`static_pass_rate`) on a small public Qiskit/OpenQASM task set - an early quality
+signal for agents and LLM workflows. The rows shown today are labelled **SAMPLE/demo**.
+
+- [`leaderboard/README.md`](https://github.com/JCQuankey/qcheck/blob/main/leaderboard/README.md) - how to add a submission and run it
+- [`leaderboard/methodology.md`](https://github.com/JCQuankey/qcheck/blob/main/leaderboard/methodology.md) - scope and methodology
+- [`leaderboard/site/leaderboard.md`](https://github.com/JCQuankey/qcheck/blob/main/leaderboard/site/leaderboard.md) - the generated table
+
+## Contributing
+
+Issues and PRs welcome - especially new failure fixtures (a real LLM-generated
+snippet that should fail but currently passes, or vice versa). Each fixture
+makes qcheck sharper and feeds the public error taxonomy.
+
+## Contact
+
+- Technical questions / maintainer contact: **dev@quankey.xyz**
+- Security issues: **security@quankey.xyz** (see [`SECURITY.md`](https://github.com/JCQuankey/qcheck/blob/main/SECURITY.md))
+
+Maintained by JCQuankey / qcheck contributors. qcheck runs locally, sends no
+telemetry, and reviews code without executing it.
+
+## License
+
+Apache-2.0.

qcheck_quantum-0.2.0/pyproject.toml

@@ -0,0 +1,53 @@
+[build-system]
+requires = ["setuptools>=61"]
+build-backend = "setuptools.build_meta"
+
+[project]
+# Distribution name: 'qcheck' is already taken on PyPI (an unrelated data-
+# validation library), so we publish as 'qcheck-quantum'. The CLI command and
+# import package both remain 'qcheck'.
+name = "qcheck-quantum"
+version = "0.2.0"
+description = "Verify LLM-generated quantum code (Qiskit / OpenQASM) statically and safely."
+readme = "README.md"
+requires-python = ">=3.9"
+license = { text = "Apache-2.0" }
+authors = [{ name = "qcheck contributors" }]
+maintainers = [{ name = "JCQuankey", email = "dev@quankey.xyz" }]
+keywords = ["quantum", "qiskit", "openqasm", "llm", "linter", "code-review", "static-analysis", "sarif"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: Apache Software License",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.9",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Topic :: Software Development :: Quality Assurance",
+    "Topic :: Scientific/Engineering :: Physics",
+]
+# v0 intentionally has ZERO runtime dependencies (stdlib only: argparse, ast).
+dependencies = []
+
+[project.optional-dependencies]
+dev = ["pytest>=7"]
+# Maintainer tooling for building/checking distributions (not needed at runtime).
+release = ["build>=1", "twine>=5"]
+
+[project.urls]
+Homepage = "https://github.com/JCQuankey/qcheck"
+Repository = "https://github.com/JCQuankey/qcheck"
+Issues = "https://github.com/JCQuankey/qcheck/issues"
+
+[project.scripts]
+qcheck = "qcheck.cli:main"
+
+[tool.setuptools]
+packages = ["qcheck"]
+
+[tool.pytest.ini_options]
+# Don't collect tests out of local build/dist copies (avoids duplicate-module
+# import errors after `python -m build`).
+norecursedirs = ["build", "dist", ".venv", "*.egg-info"]