Metadata
Release files for autoctrl 0.1.2
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 | |
|---|---|---|---|---|
| autoctrl-0.1.2.tar.gz | 7.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autoctrl-0.1.2-cp312-cp312-manylinux_2_34_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.34+ x86-64 | Details |
Total release size: 312.6 kB
Release files / autoctrl-0.1.2.tar.gz
| Download URL | autoctrl-0.1.2.tar.gz |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c81a529bf2d2be30b438085be9a1afd14cb3506226e526f582c9a463295f331
|
|
BLAKE2b-256 checksum How to use checksums |
100d90e392864b6c2d9c40b4ba712bcd23e6de5ef5e005f45f1a882b8c07dbea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
maturin/1.8.2
|
Release files / autoctrl-0.1.2-cp312-cp312-manylinux_2_34_x86_64.whl
| Download URL | autoctrl-0.1.2-cp312-cp312-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 304.7 kB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
9b61b4c653e4fe5f7e77d5077303412c9a71032d1833ac5e0b711361529d819d
|
|
BLAKE2b-256 checksum How to use checksums |
8696997a556ddd20305cf883d4af87efb628c553d2c437ac2d38641415eb835f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
maturin/1.8.2
|
Security for autoctrl 0.1.2
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.