The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for cpenormalize 0.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 | |
|---|---|---|---|---|
| cpenormalize-0.0.1.tar.gz | 1.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cpenormalize-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.5 kB
Release files / cpenormalize-0.0.1.tar.gz
| Download URL | cpenormalize-0.0.1.tar.gz |
|---|---|
| Size | 1.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67255ad553f14efd065dc36389e1187937385bca4a05433bf7181d31d774a556
|
|
BLAKE2b-256 checksum How to use checksums |
9ac36d06f637da2c1ad0f0712d6f2c0e10c15d41694cd2d81e88f8320647bdaf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / cpenormalize-0.0.1-py3-none-any.whl
| Download URL | cpenormalize-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3e5600a2b9e7063b2ea5cb2d6b45af29e6ed9d9498d64bbaa73241be23cfd32a
|
|
BLAKE2b-256 checksum How to use checksums |
07909f3b5da1c31d6a7549e0ec6a08ada47c35d09a5bd6f14a2a5e268bc2ea3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for cpenormalize 0.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.
