1 maintainer
Metadata
1 maintainer
Release files for cyclotron-std 2.0.0
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 | |
|---|---|---|---|---|
| cyclotron-std-2.0.0.tar.gz | 8.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cyclotron_std-2.0.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 16.3 kB
Release files / cyclotron-std-2.0.0.tar.gz
| Download URL | cyclotron-std-2.0.0.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e210cc813bf45c78de9f675cd0db54315e7b3a3a8ce5d5d9a211a9ebb2c9d532
|
|
BLAKE2b-256 checksum How to use checksums |
dbf5dffe22c7c6947e5e58e125954d3b812b9d82dd8da32f18c419e8fb7c237f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / cyclotron_std-2.0.0-py2.py3-none-any.whl
| Download URL | cyclotron_std-2.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
94faca86ec14cf4c97f62f4bc83275d227492f3c85df3491c9c11a9936348e66
|
|
BLAKE2b-256 checksum How to use checksums |
eb5465fa8002ad4f1c3ef410ca9ab38d124f6d2a4389962a55b9f5e517b8bd84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for cyclotron-std 2.0.0
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.
