You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Artifact-specific bundled-component attribution for cffi 1.17.1 Linux aarch64 wheel #284
Please provide, or point to existing publisher-controlled evidence for, the complete bundled or statically linked component inventory for this exact wheel: component names/versions and source references, build target/features relevant to included components, and the applicable license, copyright and notice texts, including changes introduced by patches. Please explain the relationship between that inventory and the wheel/native-member SHA256 values above, distinguishing bundled/static code from external dynamic dependencies and build-only candidates. An artifact-specific publisher statement supported by applicable primary source/notice evidence may provide this relationship; you do not need to generate new member hashes if an exact wheel binding identifies the shipped members. Conservative additional notice coverage may be useful, provided included versus merely covered components remain distinguished. A sufficiently corroborated inventory and notices are useful; a cryptographically signed attestation is optional. A source lockfile or a workflow version alone does not establish which components are present in the released bytes. If historical artifact-specific evidence is unavailable, please say so; this request does not ask you to rebuild, execute or publish a replacement artifact.
The retained Linux build workflow declares static libffi 3.4.2. Please corroborate the libffi source, patches, selected components and applicable notices for this Linux aarch64 wheel, along with any other statically bundled code. Windows libffi notice files are insufficient to attribute the Linux binary.
Thank you. Existing primary documentation or release records are welcome; please do not include private build logs, credentials or customer information.
Who is "we" and why should I put effort into this? If you are going to ask for us to do work for you, you should at least introduce yourselves and give some justification.
Activity
mattip commentedon Oct 10, 2026
Who is "we" and why should I put effort into this? If you are going to ask for us to do work for you, you should at least introduce yourselves and give some justification.