1 maintainer
Metadata
1 maintainer
Release files for xpip-upload 1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| xpip_upload-1.5.tar.gz | 4.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xpip_upload-1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.0 kB
Release files / xpip_upload-1.5.tar.gz
| Download URL | xpip_upload-1.5.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28c6be4029d86bc03d9dc913a2b2a422dbc86c682d8d7db5e8ffc0720deb1414
|
|
BLAKE2b-256 checksum How to use checksums |
93e3357bb09d519628ec260139f588bace9faeaf606cfefbea409d7a339b195f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / xpip_upload-1.5-py3-none-any.whl
| Download URL | xpip_upload-1.5-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a0536599abeb6086f6fafcacf836b2ff694ca83cc56245edd61fe5cf726259e2
|
|
BLAKE2b-256 checksum How to use checksums |
279c77c8868f73f742e80849e60db5aa0c2f30f5264ee3d67f3ce0f78e5819ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for xpip-upload 1.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
