2 maintainers
Metadata
2 maintainers
Release files for misunderstanding 0.0.1
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 | |
|---|---|---|---|---|
| misunderstanding-0.0.1.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| misunderstanding-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.5 kB
Release files / misunderstanding-0.0.1.tar.gz
| Download URL | misunderstanding-0.0.1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
41b284709189fa305dfdbad936dff9727e0d710f99ae52ef21349e7caa5c44af
|
|
BLAKE2b-256 checksum How to use checksums |
484c41036d0dcd5981befc0d80c73892c4f65854e6073f3b2fbab93b10afb118
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / misunderstanding-0.0.1-py3-none-any.whl
| Download URL | misunderstanding-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
baa4b22ea325df6bd31953f0e0ccca660a79728331b4dc7cacff742f9bc155c2
|
|
BLAKE2b-256 checksum How to use checksums |
e28c528bb35baa40c50dd1909056bf8228bcf4714c6d765cba282f21e2e4d693
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for misunderstanding 0.0.1
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.
