UNKNOWN
Metadata
Release files for chakraversiontracker 1.1.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.1.0.20160901.tar.gz | 14.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chakraversiontracker-1.1.0.20160901-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 30.6 kB
Release files / chakraversiontracker-1.1.0.20160901.tar.gz
| Download URL | chakraversiontracker-1.1.0.20160901.tar.gz |
|---|---|
| Size | 14.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d6e1ffd42cdc8983fb57e71f238a30c67d097cc7e1316dcd47222f94ff8c0ea
|
|
BLAKE2b-256 checksum How to use checksums |
299714573b8ae48f2b4fd04043e703d2e7ca83e68c3dd3aabbe3ba4e8bf4f6a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / chakraversiontracker-1.1.0.20160901-py2-none-any.whl
| Download URL | chakraversiontracker-1.1.0.20160901-py2-none-any.whl |
|---|---|
| Size | 15.9 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
9f84d13a43075ee751a04b28512944d619f46d6f23e41a4995faead2479fe59c
|
|
BLAKE2b-256 checksum How to use checksums |
5af15a65e7b96941dda56833350445d6ca9cddf1aaad8fb53b70bf8a153cee71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for chakraversiontracker 1.1.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.