1 maintainer
Metadata
1 maintainer
Release files for python3-commons 0.14.27
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 | |
|---|---|---|---|---|
| python3_commons-0.14.27.tar.gz | 114.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python3_commons-0.14.27-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 149.2 kB
Release files / python3_commons-0.14.27.tar.gz
| Download URL | python3_commons-0.14.27.tar.gz |
|---|---|
| Size | 114.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4cbf211f6f92602a001c2813a26db22260a51ae7f009558f6570ddfa54799cf6
|
|
BLAKE2b-256 checksum How to use checksums |
ec897dd6d135f043cab69ee86f3d3ed8bfcf0301fa1d5b169c0728a11c1ff9b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / python3_commons-0.14.27-py3-none-any.whl
| Download URL | python3_commons-0.14.27-py3-none-any.whl |
|---|---|
| Size | 35.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2c75b1e6ebc60fc55d9431472a74cb766573db7f9ba54365e7ee85634956b20
|
|
BLAKE2b-256 checksum How to use checksums |
65622138447268f71658270ec1ab47c336802c629049c1db8c0e2f963159c462
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for python3-commons 0.14.27
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.
