Publisher signature or attestation for the exact Windows wheel, opencv-python 4.14.0.94 · Issue #1277 · opencv/opencv-python · GitHub
Skip to content

Publisher signature or attestation for the exact Windows wheel, opencv-python 4.14.0.94 #1277

Open

Description

@luciorodrigues-tec

Hello opencv-python maintainers,

We are preparing a reproducible offline Python environment and need to locate
publisher-authenticated evidence for this existing, unmodified wheel:

Field Exact value
Package opencv-python 4.14.0.94
Filename opencv_python-4.14.0.94-cp37-abi3-win_amd64.whl
Size 41,166,165 bytes
SHA256 ace53616cdffc9643e17e075397b493e607c427d388c7508798ef7ad2ed577cc
Official repository opencv/opencv-python
Release / tag 4.14.0.94 / 94
Commit 2ba8bf6
Windows CI run 30346216575, attempt 1
CI artifact wheel-0-0-0-x64, ID 8683370453

We already established byte-for-byte equality between this PyPI wheel and the
wheel inside the official CI artifact. We retain that evidence separately from
publisher signature verification.

Could you point us to an existing signature/attestation bundle and the official
publisher verification policy for this exact wheel? We need the original signed
statement or detached signature, its certificate/public verification material,
and the required transparency or timestamp evidence. The policy should identify
the authorized public key or signer identity, issuer and predicate, as applicable,
through an official source independent of the candidate bundle itself.

Our dated public observations returned HTTP 404 for this wheel's PyPI provenance
endpoint and for the repository's GitHub attestation queries on the wheel and CI
container digests. The legacy Rekor index returned no UUIDs for those two digests.
We recognize that these results are incomplete discovery observations and do
not establish that no signature exists elsewhere.

If there is no existing proof, please let us know. If the project can issue a
new authorized publisher endorsement of the same bytes, we can assess it in a
new review while retaining its actual issue time and scope. We would not present
a later endorsement as proof that the original historical build/publication was
signed when it occurred. We are not asking for a wheel rebuild or replacement.

Only public verification material is needed; please do not provide any private
key, credential, password or access token. A pointer to the appropriate official
policy or existing artifact is sufficient for the next review.

Thank you.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions