The author of this package has not provided a project description
Metadata
Release files for asucks 0.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 | |
|---|---|---|---|---|
| asucks-0.2.0.tar.gz | 5.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asucks-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.6 kB
Release files / asucks-0.2.0.tar.gz
| Download URL | asucks-0.2.0.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc4988f95c2c77b3ec3a03a29867a1b30777a0cce06959c7ee964e39210c440f
|
|
BLAKE2b-256 checksum How to use checksums |
1c27d80cd39f5ce2d4a658eb552be4eb40057425680fd38827466dce0c3555d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.5 CPython/3.7.8 Linux/5.7.15-100.fc31.x86_64
|
Release files / asucks-0.2.0-py3-none-any.whl
| Download URL | asucks-0.2.0-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d134244320ffe00742ecdfb77166c6f08a88d5ec534290fb22a93407fd458d8
|
|
BLAKE2b-256 checksum How to use checksums |
6b70e30a400a208641997ad766bea09bc23cb515f29f446a0d73fb902326eda2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.5 CPython/3.7.8 Linux/5.7.15-100.fc31.x86_64
|
Security for asucks 0.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.