The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for autodrome 0.1.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 | |
|---|---|---|---|---|
| autodrome-0.1.0.tar.gz | 18.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autodrome-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.7 kB
Release files / autodrome-0.1.0.tar.gz
| Download URL | autodrome-0.1.0.tar.gz |
|---|---|
| Size | 18.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dbc2678eb8d39e1bec03d97b2e870f883d578c05e609f04c7ed090e00e333be5
|
|
BLAKE2b-256 checksum How to use checksums |
535b23254ad91da46bf9234c70244d0621bdf3f3e94d94133c23a4f60563abc0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.6
|
Release files / autodrome-0.1.0-py3-none-any.whl
| Download URL | autodrome-0.1.0-py3-none-any.whl |
|---|---|
| Size | 25.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6752eee32de4033063a59e2ea181305dedd526333c843a2ecf7e5b3092411d73
|
|
BLAKE2b-256 checksum How to use checksums |
bed861e66a5fca140930002a8ebdddaaa9cde6d6fad6d9491d76bae2e08943db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.6
|
Security for autodrome 0.1.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.
