This is a brief description
1 maintainer
Metadata
1 maintainer
Release files for ethansrokalib 0.0.2
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 | |
|---|---|---|---|---|
| ethansrokalib-0.0.2.tar.gz | 834 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ethansrokalib-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.2 kB
Release files / ethansrokalib-0.0.2.tar.gz
| Download URL | ethansrokalib-0.0.2.tar.gz |
|---|---|
| Size | 834 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba6cdb4563ceb45ab21c0285cd476137d173da4df141ce763969ef6166aff7ea
|
|
BLAKE2b-256 checksum How to use checksums |
01b9e6f2d14ffde7487b413d4f239d59d06ddea63f9e91d885a0fd5424d6f34f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.15
|
Release files / ethansrokalib-0.0.2-py3-none-any.whl
| Download URL | ethansrokalib-0.0.2-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ecef32d628aee67b403dae3ca8e79dfe1fb4e633075e6f0272bb64b02e23d3fa
|
|
BLAKE2b-256 checksum How to use checksums |
85fdb393f24c8945dc9b3df0a2467c31ff6634cff34f0481d3bdd5700a7250ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.15
|
Security for ethansrokalib 0.0.2
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.
