The author of this package has not provided a project description
Metadata
Release files for speterlin-crypto 1.2.0
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 | |
|---|---|---|---|---|
| speterlin_crypto-1.2.0.tar.gz | 38.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| speterlin_crypto-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.5 kB
Release files / speterlin_crypto-1.2.0.tar.gz
| Download URL | speterlin_crypto-1.2.0.tar.gz |
|---|---|
| Size | 38.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
375f62eed58202b53f125b27937d7c7ddbe2088f53f4a4cbdc41958d64efcfe7
|
|
BLAKE2b-256 checksum How to use checksums |
59eada2e3b35749d3c654a4cbba9866966f13605abca2585496e33a5f3086d39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.1
|
Release files / speterlin_crypto-1.2.0-py3-none-any.whl
| Download URL | speterlin_crypto-1.2.0-py3-none-any.whl |
|---|---|
| Size | 36.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00be7b052f65c1251b75384913488ab99163c2ea0ecb18a00510ebf2c0681925
|
|
BLAKE2b-256 checksum How to use checksums |
22e4040c6fda7c002b9300689221b8319c1cb5481e18aeb68eee7e12e1141ef3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.1
|
Security for speterlin-crypto 1.2.0
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.