-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
PEP 815: Deprecate RECORD.jws and RECORD.p7s
#4727
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
AA-Turner
merged 9 commits into
python:main
from
konstin:konsti/deprecate-record-signatures
Dec 5, 2025
Merged
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
964ad05
PEP 815: Deprecate `RECORD.jws` and `RECORD.p7s`
konstin 493b350
Update .github/CODEOWNERS
konstin 90ac2bc
Update peps/pep-0815.rst
konstin b357fa3
Update peps/pep-0815.rst
konstin 8dc69f2
Update peps/pep-0815.rst
konstin f0fc29b
Partially apply suggestion
konstin 54ce994
Partially apply suggestion
konstin c76f4d1
Backwards Compatibility for build backends
konstin ad90318
Two blank lines between section
konstin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,70 @@ | ||
| PEP: 815 | ||
| Title: Deprecate ``RECORD.jws`` and ``RECORD.p7s`` | ||
| Author: Konstantin Schütze <konstin@mailbox.org>, | ||
| William Woodruff <william@yossarian.net> | ||
| Sponsor: Emma Harper Smith <emma@python.org> | ||
| PEP-Delegate: Paul Moore <p.f.moore@gmail.com> | ||
| Status: Draft | ||
| Type: Standards Track | ||
| Topic: Packaging | ||
| Created: 04-Dec-2025 | ||
| Post-History: `09-Jun-2025 <https://discuss.python.org/t/discouraging-deprecating-pep-427-style-signatures/94968>`__ | ||
|
konstin marked this conversation as resolved.
Outdated
|
||
|
|
||
| Abstract | ||
| ======== | ||
|
|
||
| This PEP deprecates the ``RECORD.jws`` and ``RECORD.p7s`` wheel signature | ||
| files. Lack of support in tooling means that these virtually unused files do | ||
| not provide the security they purport. Users looking for wheel signing should | ||
| instead refer to | ||
| :ref:`index hosted attestations <packaging:index-hosted-attestations>`. | ||
|
konstin marked this conversation as resolved.
Outdated
|
||
|
|
||
| Motivation | ||
| ========== | ||
|
|
||
| No major Python packaging tool supports generating or checking either | ||
| ``RECORD.jws`` or ``RECORD.p7s``. Notably, neither pip nor uv validate the | ||
| hashes in ``RECORD``, a requirement for using signature files. The | ||
| :ref:`binary distribution format <packaging:binary-distribution-format>` | ||
| presents them as security features, potentially resulting in user confusion. | ||
|
|
||
| The state of the art for hashing and signing wheels has shifted from | ||
| in-archive information to out-of-archive information presented on the index, | ||
| such as hashes and :ref:`attestations <packaging:index-hosted-attestations>` | ||
| in the :ref:`simple repository API <packaging:simple-repository-api>`. Unlike | ||
| the hashes in ``RECORD``, tools such as pip and uv validate index provided | ||
| hashes. | ||
|
|
||
| Both files are virtually unused. A GitHub search for ``path:**.dist-info/RECORD`` | ||
| yields 635k results, ``path:**.dist-info/RECORD.jws`` has 8 distinct results | ||
| and ``path:**.dist-info/RECORD.p7s`` has zero results. | ||
|
AA-Turner marked this conversation as resolved.
|
||
|
|
||
| Specification | ||
| ============= | ||
|
|
||
| The ``RECORD.jws`` and ``RECORD.p7s`` files are deprecated, and the | ||
| :ref:`binary distribution format <packaging:binary-distribution-format>` is | ||
| updated to reflect this. Build backends and other tools must not add these | ||
| files to wheels. Installers must not attempt to verify them, while they | ||
| remain excluded from ``RECORD``. | ||
|
AA-Turner marked this conversation as resolved.
Outdated
|
||
|
|
||
| Backward Compatibility | ||
| ====================== | ||
|
konstin marked this conversation as resolved.
Outdated
|
||
|
|
||
| Known implementations require no changes, as they do not support these files | ||
| beyond skipping them when processing the ``RECORD`` file. Users should refer | ||
| to :ref:`index hosted attestations <packaging:index-hosted-attestations>` for | ||
| signing archives. | ||
|
AA-Turner marked this conversation as resolved.
Outdated
|
||
|
|
||
| Security Implications | ||
| ===================== | ||
|
|
||
| This PEP strengthens the security of the Python packaging ecosystem by | ||
| reducing the divergence between security features presented in the | ||
| specification and the security features supported by tools. | ||
|
|
||
| Copyright | ||
| ========= | ||
|
|
||
| This document is placed in the public domain or under the | ||
| CC0-1.0-Universal license, whichever is more permissive. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.