This release is a pre-release and may not be stable for production use.
Metadata
1 maintainer
Release files for certs 0.1a1
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 | |
|---|---|---|---|---|
| certs-0.1a1.tar.gz | 9.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| certs-0.1a1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 18.0 kB
Release files / certs-0.1a1.tar.gz
| Download URL | certs-0.1a1.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b07445a8e75c222da4ce527b8ec14e25bdb010420688be0f8e88491a862ac0b1
|
|
BLAKE2b-256 checksum How to use checksums |
bdbd5922a1595e5d63aa06bffb2e3054fad690c161a0b232bb98070bd418779d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Release files / certs-0.1a1-py2.py3-none-any.whl
| Download URL | certs-0.1a1-py2.py3-none-any.whl |
|---|---|
| Size | 9.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
3c63267d4554abdd57e10c63c72a382b4d4cb8df467f4f677706f0026dfba8e0
|
|
BLAKE2b-256 checksum How to use checksums |
fae4f211d66558edd144655c4c96daf3ebf4c96adefd2ec4a07c344d908e0e96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Security for certs 0.1a1
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.
