The author of this package has not provided a project description
Metadata
Release files for applying-cli 0.0.3
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 | |
|---|---|---|---|---|
| applying-cli-0.0.3.tar.gz | 1.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| applying_cli-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.6 kB
Release files / applying-cli-0.0.3.tar.gz
| Download URL | applying-cli-0.0.3.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ca6df4799a43994d95859ac7f5e5a4b509ee35861d8d3ebbfde83324c6154400
|
|
BLAKE2b-256 checksum How to use checksums |
9515c3376e132a9353192c9b5a1686bd9d20fefcfade01149916ffbda839afea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.16
|
Release files / applying_cli-0.0.3-py3-none-any.whl
| Download URL | applying_cli-0.0.3-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2aa98b2a55eb4c5afe6180c9eed05ee755e108a11c9227422e35ff22f47ab6dd
|
|
BLAKE2b-256 checksum How to use checksums |
e18ed93ffd25bfbd7a2c5dbeee8d480dac3c401734173e853188cb0505e30dbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.16
|
Security for applying-cli 0.0.3
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.