The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for autorunner2 1.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 | |
|---|---|---|---|---|
| autorunner2-1.0.0.tar.gz | 68.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autorunner2-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 160.6 kB
Release files / autorunner2-1.0.0.tar.gz
| Download URL | autorunner2-1.0.0.tar.gz |
|---|---|
| Size | 68.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
600295a587267949baad63ae596e3db071a7614b6eb3ec9dcd5301755a920973
|
|
BLAKE2b-256 checksum How to use checksums |
e0a567216dc465cc6dcadfcb13fb9f0de6bec39f5573c9e0122d820e33bf4783
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.11
|
Release files / autorunner2-1.0.0-py3-none-any.whl
| Download URL | autorunner2-1.0.0-py3-none-any.whl |
|---|---|
| Size | 92.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b96fcebe2fe1e90ea55581280b59fcc8d8435732d35ad2ec860af8059f1a505
|
|
BLAKE2b-256 checksum How to use checksums |
e6d139e1672eaf3143ccf074baec44eb9988701a22e891d9e2eaa2091fb249a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.11
|
Security for autorunner2 1.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.
