UNKNOWN
1 maintainer
Metadata
1 maintainer
Release files for colorizer-py 0.1.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 | |
|---|---|---|---|---|
| colorizer-py-0.1.1.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| colorizer_py-0.1.1-cp27-none-macosx_10_11_intel.whl | CPython 2.7 | none | macOS 10.11+ Intel (x86-64, i386) | Details |
Total release size: 3.5 kB
Release files / colorizer-py-0.1.1.tar.gz
| Download URL | colorizer-py-0.1.1.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc28f55510c1aa994f97af73e1dc5a13ad26fbcfa4f0b0c41a3884967697b064
|
|
BLAKE2b-256 checksum How to use checksums |
0f1b3d38aa725a3c65d6ce23bf8deecd501a795c82a20bd53c29a049400e252c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / colorizer_py-0.1.1-cp27-none-macosx_10_11_intel.whl
| Download URL | colorizer_py-0.1.1-cp27-none-macosx_10_11_intel.whl |
|---|---|
| Size | 2.2 kB |
| Tags | CPython 2.7 macOS 10.11+ Intel (x86-64, i386) |
|
SHA-256 checksum How to use checksums |
1506b056629855cadf5620d56c35d91cca448acbf8db19e2fa2b92fd44de2fdd
|
|
BLAKE2b-256 checksum How to use checksums |
49e2cd3fb37ee5ca6695d517782667be8cf25b06804950d1ea1809044769844b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for colorizer-py 0.1.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.
