wheel-crypto-scan 0.1.0__tar.gz

wheel_crypto_scan-0.1.0/.github/dependabot.yml

@@ -0,0 +1,28 @@
+# Dependabot configuration.
+#
+# The important one is github-actions. Every action in .github/workflows is pinned to a
+# full commit SHA, which is what stops a compromised tag from reaching CI, and which
+# also means nothing updates unless something updates it. That something is Dependabot.
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Wait 3 days after a new action version is published before opening a PR.
+    # Gives time for supply chain compromises to be caught. Security updates
+    # are exempt and arrive immediately.
+    cooldown:
+      default-days: 3
+    open-pull-requests-limit: 10
+
+  # Runtime dependencies are declared with open lower bounds (pyelftools>=0.31), so
+  # this stays quiet until something is pinned or a lower bound actually blocks a
+  # release. It is here so that the day one is pinned, it is already watched.
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    cooldown:
+      default-days: 3
+    open-pull-requests-limit: 5

wheel_crypto_scan-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,126 @@
+name: CI
+
+on:
+  push:
+    branches: ["**"]
+    tags-ignore: ["**"]
+  pull_request:
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+env:
+  FORCE_COLOR: "1"
+
+jobs:
+  test:
+    name: tests (py${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          fetch-depth: 0
+          fetch-tags: true
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+      - name: Install Python ${{ matrix.python-version }}
+        run: uv python install ${{ matrix.python-version }}
+      - name: Run tests
+        run: uvx --with tox-uv tox -e py$(echo '${{ matrix.python-version }}' | tr -d .)
+
+  lint:
+    name: ruff
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          fetch-depth: 0
+          fetch-tags: true
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+      - name: Lint and format check
+        run: uvx --with tox-uv tox -e lint
+
+  pylint:
+    name: pylint
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          fetch-depth: 0
+          fetch-tags: true
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+      - run: uv python install 3.12
+      - name: Run pylint
+        run: uvx --with tox-uv tox -e pylint
+
+  build:
+    name: build and verify the distribution
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          fetch-depth: 0
+          fetch-tags: true
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+      - name: Build sdist and wheel
+        run: uv build
+      - name: Check metadata
+        run: uvx twine check --strict dist/*
+      - name: Confirm the ruleset and schema ship in the wheel
+        run: |
+          set -euo pipefail
+          python3 -m zipfile -l dist/*.whl | tee /dev/stderr | grep -q 'data/ruleset.toml'
+          python3 -m zipfile -l dist/*.whl | grep -q 'data/schema.json'
+
+  determinism:
+    name: byte-identical output across interpreters
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          fetch-depth: 0
+          fetch-tags: true
+          persist-credentials: false
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: true
+      - run: uv python install 3.11 3.14
+      - name: Build the corpus
+        run: uv run --python 3.12 python tools/make_corpus.py corpus 40
+      - name: Scan under 3.11 and 3.14
+        run: |
+          set -euo pipefail
+          for v in 3.11 3.14; do
+            uv run --python "$v" --with pyelftools --with packaging \
+              python -m wheel_crypto_scan scan corpus -o "out-$v.jsonl" \
+              --jobs 4 --no-cache --quiet
+          done
+      - name: Assert the bytes match
+        run: |
+          set -euo pipefail
+          if ! cmp out-3.11.jsonl out-3.14.jsonl; then
+            echo "::error::scan output differs between Python 3.11 and 3.14"
+            diff <(jq -S . out-3.11.jsonl) <(jq -S . out-3.14.jsonl) | head -40
+            exit 1
+          fi
+          echo "identical: $(wc -l < out-3.11.jsonl) records, sha256 $(sha256sum < out-3.11.jsonl)"

wheel_crypto_scan-0.1.0/.github/workflows/pypi.yml

@@ -0,0 +1,71 @@
+name: Publish to PyPI
+
+# Publishes on a bare semver tag and nothing else:
+#
+#     git tag -a 0.1.0 -m "0.1.0" && git push origin 0.1.0
+#
+# The version comes from the tag through uv-dynamic-versioning, so there is no number
+# in the repository to bump and nothing to keep in sync.
+#
+# Authentication is PyPI Trusted Publishing (OIDC); there is no API token to store.
+
+on:
+  push:
+    tags:
+      - '[0-9]+.[0-9]+.[0-9]+'
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    name: Run Tox
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          fetch-depth: 0
+          fetch-tags: true
+          persist-credentials: false
+      - name: Install uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+      - name: Install interpreters
+        run: uv python install 3.11 3.12 3.13 3.14
+      # A tag can point at any commit, and CI does not run on tags, so the release
+      # path verifies the thing it is about to publish rather than assuming.
+      - name: Run all envs
+        run: uvx --with tox-uv tox
+
+  build-and-publish:
+    name: Build and publish to PyPI
+    needs: test
+    if: ${{ github.repository_owner == 'EmilienM' }}
+
+    runs-on: ubuntu-latest
+    environment: release
+
+    permissions:
+      contents: read
+      id-token: write
+
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          # Full history and tags: the version is derived from the tag.
+          fetch-depth: 0
+          fetch-tags: true
+          persist-credentials: false
+      - name: Install uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+      - name: Build sdist and wheel
+        run: uv build
+      - name: Check metadata
+        run: uvx twine check --strict dist/*
+      - name: Confirm the ruleset and schema ship in the distribution
+        run: |
+          set -euo pipefail
+          python3 -m zipfile -l dist/*.whl | grep -q 'data/ruleset.toml'
+          python3 -m zipfile -l dist/*.whl | grep -q 'data/schema.json'
+      - name: Publish to PyPI
+        if: startsWith(github.ref, 'refs/tags')
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2

wheel_crypto_scan-0.1.0/.gitignore

@@ -0,0 +1,12 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+build/
+dist/
+.tox/
+.venv/
+.pytest_cache/
+.ruff_cache/
+# Local scan corpus and outputs, never committed.
+.corpus/
+*.jsonl

wheel_crypto_scan-0.1.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 [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.

wheel_crypto_scan-0.1.0/NOTICE

@@ -0,0 +1,9 @@
+wheel-crypto-scan
+Copyright 2026 Red Hat, Inc.
+
+This product includes software developed at Red Hat, Inc.
+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

wheel_crypto_scan-0.1.0/PKG-INFO

@@ -0,0 +1,178 @@
+Metadata-Version: 2.5
+Name: wheel-crypto-scan
+Version: 0.1.0
+Summary: Deterministic FIPS-risk evidence inspector for Python wheels
+Author-email: Emilien Macchi <emacchi@redhat.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: crypto,fips,sbom,supply-chain,wheel
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Security :: Cryptography
+Requires-Python: >=3.11
+Requires-Dist: packaging>=23.2
+Requires-Dist: pyelftools>=0.31
+Description-Content-Type: text/markdown
+
+# wheel-crypto-scan
+
+Reports crypto-relevant **evidence** found inside Python wheels, so the teams consuming a
+package index can see per-wheel FIPS risk before they ship it.
+
+It gathers evidence. It does not decide compliance.
+
+## What it answers
+
+The question it exists for: **does this wheel use the system OpenSSL, or does it carry its
+own?** A wheel that resolves `libcrypto.so.3` from the host inherits the host's FIPS
+provider and crypto policy. A wheel that ships or statically links its own copy does not,
+and no amount of host configuration changes that.
+
+There are three ways a wheel can carry its own OpenSSL, and all three are caught:
+
+| Evidence | `openssl_linkage` |
+|---|---|
+| Plain `DT_NEEDED libcrypto.so.3`, OpenSSL symbols imported | `system` |
+| A library under `*.libs/` or `.dylibs/`, or a dependency on a hash-renamed `libcrypto-3a1f2b4c.so.3` | `bundled` |
+| No dependency and no vendor directory, but OpenSSL symbols defined or its version banner in read-only data | `static` |
+
+The third case is the one that matters most and the one a vendor-directory check alone
+misses. Run against three real builds of `cryptography`:
+
+```
+Fedora RPM build      DT_NEEDED libcrypto.so.3, libssl.so.3    64 symbols imported   -> system
+PyPI 42.0.5           empty cryptography.libs/, no DT_NEEDED,  0 symbols exported    -> static
+PyPI 3.4.8            no DT_NEEDED, no vendor directory,       0 symbols exported    -> static
+```
+
+For PyPI 42.0.5 the *only* evidence is the `OpenSSL 3.2.1` banner in `.rodata`: the vendor
+directory is empty, nothing is declared, and the symbols are hidden by a version script.
+
+## What it explicitly does not do
+
+- **It never says "FIPS compliant."** The verdict taxonomy has no passing class and cannot
+  acquire one. A human makes that call.
+- **No LLM at runtime.** Pure static analysis. The JSON is what gets fed to a model later,
+  as a separate step.
+- **No dataflow or reachability analysis.** It records the call site; it does not try to
+  prove the call runs.
+- **No container images, no RPMs, no sdists.** Wheels only.
+- **No network**, except an explicitly requested `--index-url` download of the wheels.
+
+## Install and run
+
+```bash
+uv tool install .                       # or: uv run wheel-crypto-scan
+wheel-crypto-scan scan /path/to/wheels -o index.jsonl --jobs 8
+wheel-crypto-scan scan one.whl --format md
+wheel-crypto-scan rules                 # the rule table, for review
+wheel-crypto-scan schema                # the JSON Schema for the output
+```
+
+Useful flags: `--jobs N`, `--cache-dir DIR` / `--no-cache`, `--resume`, `--evidence-level
+minimal|standard`, `--ruleset PATH`, `--from-file LIST`, `--index-url URL --download-dir DIR`.
+
+Triage the output with `jq`:
+
+```bash
+jq -r 'select(.verdict.conditions.openssl_linkage == "bundled") | .wheel.filename' index.jsonl
+jq -r 'select(.verdict.class == "FIPS_BREAKING") | "\(.wheel.name) \(.verdict.reasons[0])"' index.jsonl
+jq -r 'select(.verdict.class == "OPAQUE") | .wheel.filename' index.jsonl   # could not be read
+```
+
+## Output
+
+JSONL, one record per wheel. `SCHEMA.md` documents every field and the versioning rules;
+`wheel-crypto-scan schema` prints the machine-readable JSON Schema.
+
+| Verdict class | Meaning |
+|---|---|
+| `NON_APPROVED_CRYPTO` | Implements or bundles a non-FIPS-approved primitive |
+| `CONDITIONAL` | Approved only under a stated condition; `verdict.conditions` says which holds |
+| `FIPS_BREAKING` | Will raise at runtime under FIPS-enforcing mode |
+| `CONTEXT_DEPENDENT` | Non-approved primitive that may be a non-security use |
+| `NO_CRYPTO_DETECTED` | Nothing found. Absence of evidence, not evidence of absence |
+| `OPAQUE` | Stripped, unreadable or source-free. Cannot determine |
+
+A wheel that could not be read is `OPAQUE`, never `NO_CRYPTO_DETECTED`. That distinction is
+enforced by a test asserting every recordable failure has a rule.
+
+## The ruleset
+
+All policy lives in [`src/wheel_crypto_scan/data/ruleset.toml`](src/wheel_crypto_scan/data/ruleset.toml).
+Every package name, symbol, string, crate, library and verdict is data, each with a `why`
+explaining in plain language what it is and why it is flagged. A crypto engineer can review
+and edit it without reading any Python. `wheel-crypto-scan rules` renders it for review.
+
+Bump `ruleset_version` after editing: it is part of the scan cache key, so bumping it is
+what makes previously scanned wheels get re-evaluated.
+
+## Determinism
+
+Same wheel in, byte-identical JSONL out. Verified on a 100-wheel corpus to be identical
+across repeat runs, `--jobs 1` vs `--jobs 8`, cold vs warm cache, and Python 3.11, 3.12,
+3.13 and 3.14. Output is sorted, ASCII-only, float-free, and contains no host paths,
+timestamps or hostnames.
+
+One caveat worth knowing: `ast.parse` follows the grammar of the interpreter running it,
+so a wheel using syntax newer than the scanner's interpreter will not parse. **Pin the
+interpreter** if you need output comparable across hosts. That difference is never
+silently favourable: unparsed files are counted in `artifacts.py_files_unparsed`, and a
+wheel whose every source file failed reports `source_available: false` and comes out
+`OPAQUE`, not clean.
+
+## Performance
+
+Measured on 100 synthetic wheels averaging 3.3 MiB uncompressed, on 16 cores:
+
+| Mode | wheels/s | per wheel |
+|---|---|---|
+| `--jobs 1`, cold | 3.1 | 320 ms |
+| `--jobs 4`, cold | 11.8 | 85 ms |
+| `--jobs 8`, cold | 20.4 | 49 ms |
+| `--jobs 8`, warm cache | 674 | 1.5 ms |
+
+Wheels are read from the zip in memory and never extracted to disk. Members above the
+in-memory threshold stream through a seekable zip reader that retains a bounded window of
+what it has already decompressed, so a multi-gigabyte extension costs a bounded number of
+passes rather than a gigabyte of resident memory. Reading the real 5.5 MiB
+`libcrypto.so.3` through that path takes 0.19 s with one decompression; without the
+window it took 17 s and 3,161.
+
+## Development
+
+```bash
+uvx --with tox-uv tox          # tests across py311-py314, plus ruff lint and format
+uvx --with tox-uv tox -e lint
+```
+
+Test fixtures are synthesised, including the ELF objects: the suite needs no compiler, no
+network and no committed binaries, and runs byte-identically anywhere. Tests against real
+downloaded wheels are behind the `real` marker; tests that read host system libraries are
+behind `hostbin`.
+
+Dependencies are `pyelftools` and `packaging`, and nothing else without asking.
+
+### Releasing
+
+Publishing is triggered by a bare semver tag and nothing else. There is no version to
+bump: it is derived from the tag at build time by `uv-dynamic-versioning`, so the
+version in a record is always the version that produced it.
+
+```bash
+git tag -a 0.1.0 -m "0.1.0" && git push origin 0.1.0
+```
+
+No `v` prefix. The workflow re-runs the full matrix, builds, checks that the ruleset and
+schema are actually inside the distribution, and uploads through PyPI Trusted
+Publishing, so there is no token to store.
+
+An untagged build reports its commit, for example `0.0.0.post14.dev0+1105fe9`, which
+makes it obvious when a record came from something other than a release.
+
+## Licence
+
+Apache 2.0. See [LICENSE](LICENSE).