The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pypomes-cs 1.0.2
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.2.tar.gz | 29.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pypomes_cs-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.5 kB
Release files / pypomes_cs-1.0.2.tar.gz
| Download URL | pypomes_cs-1.0.2.tar.gz |
|---|---|
| Size | 29.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a03139e237623590bc704a1138274815382cbc23954980cfc5f88e7419c67973
|
|
BLAKE2b-256 checksum How to use checksums |
5c150513f669762b97b524f086a12332e13b0128155e5e48d44a0ed3a9cf0af0
|
| 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.2-py3-none-any.whl
| Download URL | pypomes_cs-1.0.2-py3-none-any.whl |
|---|---|
| Size | 33.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be94bbefbd0c81c40f91537961a59ec435387c61d30e286f9ff311832a0eed39
|
|
BLAKE2b-256 checksum How to use checksums |
55dc014ef8b70cba7147e883924e21667a0a8f647b449624b617211dba39475e
|
| 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.2
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.
