Metadata
Release files for ccsid1153-codec 0.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 | |
|---|---|---|---|---|
| ccsid1153_codec-0.0.2.tar.gz | 9.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ccsid1153_codec-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.6 kB
Release files / ccsid1153_codec-0.0.2.tar.gz
| Download URL | ccsid1153_codec-0.0.2.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf42bb57a61807ca06eac1cbd2d30b9a659c2d40b4ec749fb026199d527529bf
|
|
BLAKE2b-256 checksum How to use checksums |
54f739144853429279a95281e8032d5cd1551110acbf86719838b49509fd8324
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / ccsid1153_codec-0.0.2-py3-none-any.whl
| Download URL | ccsid1153_codec-0.0.2-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa1a6c8c903f02302abfee192277f9d9d32a94ab968002139a085dd7ecd3b651
|
|
BLAKE2b-256 checksum How to use checksums |
2e16b514011169ae9084c8767868171fa40874030f2f06f9e5bd72b8c707be83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for ccsid1153-codec 0.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.