CHANGELOG: More minor bug fixes. (splist)
Metadata
Release files for ZefroinLibrary 0.0.6
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 | |
|---|---|---|---|---|
| ZefroinLibrary-0.0.6.tar.gz | 1.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ZefroinLibrary-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.0 kB
Release files / ZefroinLibrary-0.0.6.tar.gz
| Download URL | ZefroinLibrary-0.0.6.tar.gz |
|---|---|
| Size | 1.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31f95850d48764c249b1dc1bf195a9263171ef9535ea95d55cf74a6e7937a23f
|
|
BLAKE2b-256 checksum How to use checksums |
6832f47ca70483268bb06864a20300f3a33a18b73e188ad70dc71a65a5475029
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.12
|
Release files / ZefroinLibrary-0.0.6-py3-none-any.whl
| Download URL | ZefroinLibrary-0.0.6-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e60e06659a676879e91efee63b171cd5cac1d5dd79e6c4e6a7c29f545a3f5743
|
|
BLAKE2b-256 checksum How to use checksums |
d0063f17104607976751768bba24a56f3a40919fcb4645927b006e65d6861fdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.12
|
Security for ZefroinLibrary 0.0.6
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.