UNKNOWN
Metadata
Release files for chakraversiontracker 1.0.0.20160901
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.0.0.20160901.tar.gz | 12.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chakraversiontracker-1.0.0.20160901-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 28.1 kB
Release files / chakraversiontracker-1.0.0.20160901.tar.gz
| Download URL | chakraversiontracker-1.0.0.20160901.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bef30b1a5197c5e3dd914a7cc1d88d05dba88ab4be65a50b1b585a4c8465bf6b
|
|
BLAKE2b-256 checksum How to use checksums |
4bbfa09b758d6ab37287e9c89ad2a83c71cc4e413ef33d767fbe7fab09d23db7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / chakraversiontracker-1.0.0.20160901-py2-none-any.whl
| Download URL | chakraversiontracker-1.0.0.20160901-py2-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
922886c407e5c767bd5479b53b6bc566aae77f10c84be7b281f9ef74b7d33962
|
|
BLAKE2b-256 checksum How to use checksums |
7d6cab2be0c790f2da747a6dde9b78b24ba918f289b63bdf0fcc3416322074ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for chakraversiontracker 1.0.0.20160901
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.