The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pypomes-cs 1.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 | |
|---|---|---|---|---|
| pypomes_cs-1.0.1.tar.gz | 29.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pypomes_cs-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.6 kB
Release files / pypomes_cs-1.0.1.tar.gz
| Download URL | pypomes_cs-1.0.1.tar.gz |
|---|---|
| Size | 29.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
434c7537e81d508a1c30dd320a0b9e20c04a81e6fefec4b611368e11333a7a75
|
|
BLAKE2b-256 checksum How to use checksums |
915e1268f0135a7c6e48d736b877f7db597c6469cadc368c1d9009821762fc83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Release files / pypomes_cs-1.0.1-py3-none-any.whl
| Download URL | pypomes_cs-1.0.1-py3-none-any.whl |
|---|---|
| Size | 33.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ced35354ebb60e783dee1fe1862f2b9cafab0d3568b3e09b9a2929a2163de4c
|
|
BLAKE2b-256 checksum How to use checksums |
939186b55a96089f8eb9f9411374e0a439a9e70123d424f3365c47675dbc3580
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Security for pypomes-cs 1.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.
