UNKNOWN
Metadata
Release files for chakraversiontracker 1.2.1.20160917
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 | |
|---|---|---|---|---|
| chakraversiontracker-1.2.1.20160917.tar.gz | 23.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chakraversiontracker-1.2.1.20160917-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.1 kB
Release files / chakraversiontracker-1.2.1.20160917.tar.gz
| Download URL | chakraversiontracker-1.2.1.20160917.tar.gz |
|---|---|
| Size | 23.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f94aeac439a04a98c5eeeb89a5c0d91edd058af192b7622b5f88b275e23baae5
|
|
BLAKE2b-256 checksum How to use checksums |
f8e7606b86f30a187510aad2ea7b9c69fb6bd25adabdb895af7b4892823f4d12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / chakraversiontracker-1.2.1.20160917-py3-none-any.whl
| Download URL | chakraversiontracker-1.2.1.20160917-py3-none-any.whl |
|---|---|
| Size | 23.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6068ec5f5eb1fa949316fe978fa5e05141a34e7b6aec53afda619d36c1e72911
|
|
BLAKE2b-256 checksum How to use checksums |
1ebd415c36ffe59a99a774e63bc0ea25dd32b249918483968f0e5eaa6b08cab3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for chakraversiontracker 1.2.1.20160917
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.