The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for autoops 0.2.5
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 | |
|---|---|---|---|---|
| autoops-0.2.5.tar.gz | 5.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autoops-0.2.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.9 kB
Release files / autoops-0.2.5.tar.gz
| Download URL | autoops-0.2.5.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ef29774b6dda4ebb39cf91a3280b05ec5d76ad83ee8818d6e2323c8bd0d9b73
|
|
BLAKE2b-256 checksum How to use checksums |
3892fbbdcf10031ab0ede73860bf6c0a36919d83c2a3e4e42bf0d80de99fa44c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.19
|
Release files / autoops-0.2.5-py3-none-any.whl
| Download URL | autoops-0.2.5-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7f0168086678515415903ebf80fc3713b0f32e400de16a8944c336912408c2b
|
|
BLAKE2b-256 checksum How to use checksums |
8f1f55386874cc342c9cbe3351310654f643e5545ed5edcc8ab05356a42f446c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.19
|
Security for autoops 0.2.5
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.
