Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#1,277 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
35/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github-actions, python
領域
release, security

調査の方向性

Start by reviewing the repository’s release and Windows CI workflow for the specified wheel and run, then check the official PyPI and GitHub attestation sources named in the issue. Determine whether an existing signature or attestation and an independent publisher verification policy cover the exact wheel bytes. Done means providing an official pointer to both, or confirming that no existing proof was found.

索引モデルが issue の本文から書いたものです。

説明

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 2ba8bf62f2f1215ab620416b041c9659005fa25c
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.

主要言語
Python
スター
5.4k
フォーク
1.1k
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

opencv/opencv-python のほかの issue

opencv/opencv-python の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。