1 maintainer
Metadata
1 maintainer
Release files for stupidwallet 0.1.16
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 | |
|---|---|---|---|---|
| stupidwallet-0.1.16.tar.gz | 16.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| stupidwallet-0.1.16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.2 kB
Release files / stupidwallet-0.1.16.tar.gz
| Download URL | stupidwallet-0.1.16.tar.gz |
|---|---|
| Size | 16.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9209ac9823d5f8918bd1c708246b9cdc3c5a373496e4663211460b22db76a62e
|
|
BLAKE2b-256 checksum How to use checksums |
49954380f9ee1eeffd1c063e50a3cb37fdcc161b5afaff98925a10bf30ef9437
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.4 Windows/11
|
Release files / stupidwallet-0.1.16-py3-none-any.whl
| Download URL | stupidwallet-0.1.16-py3-none-any.whl |
|---|---|
| Size | 17.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3c9d40d6c5aada291892b17e1483a4151ea95ed4995098eb975da4d58b64d5ca
|
|
BLAKE2b-256 checksum How to use checksums |
e5eb69f0f761c01cdcafe72e28660884f688e264b68be91a1eae9e539a547531
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.4 Windows/11
|
Security for stupidwallet 0.1.16
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.
