The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for auto-setup 0.1.1
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 | |
|---|---|---|---|---|
| auto_setup-0.1.1.tar.gz | 3.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auto_setup-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.6 kB
Release files / auto_setup-0.1.1.tar.gz
| Download URL | auto_setup-0.1.1.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0091bceace366e34e4c054d8fa44826fa1fe2428a0bd55669bf29febd432be6c
|
|
BLAKE2b-256 checksum How to use checksums |
ef2f7dffb3797ca953e21b1de72f11579ff745c012193af3c1817fef6979b0b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.3
|
Release files / auto_setup-0.1.1-py3-none-any.whl
| Download URL | auto_setup-0.1.1-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8bc3a9f6bd11d96bcc435adcbb09915fc49913103a19042a4577abedd73f0a48
|
|
BLAKE2b-256 checksum How to use checksums |
4054e49c73b2856e4284f6685b343f7c0d9d3c63b366d6c5fb04ef0558fe004f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.3
|
Security for auto-setup 0.1.1
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.
