The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pomo-cli 1.0.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 | |
|---|---|---|---|---|
| pomo_cli-1.0.0.tar.gz | 3.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pomo_cli-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.7 kB
Release files / pomo_cli-1.0.0.tar.gz
| Download URL | pomo_cli-1.0.0.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
19e878fea4ade9a7cff75347d0c6ef80bb61ed42309b34fad79d004a4f64dbaf
|
|
BLAKE2b-256 checksum How to use checksums |
ea10fb07f0ed292fe3acad923f0afd03b09151d73abeb51c1e7eb32c9d626178
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Release files / pomo_cli-1.0.0-py3-none-any.whl
| Download URL | pomo_cli-1.0.0-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4ff252ad3818370431e8b30ec7dbdc5a9e08deaacc8e3c92375b60f5a64461b1
|
|
BLAKE2b-256 checksum How to use checksums |
13e7322393a0d7514c60dab05a803f57df3d01dcc0d17c6d7faee434c8f3bbd5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Security for pomo-cli 1.0.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.
