The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for autospares 0.0.7
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 | |
|---|---|---|---|---|
| autospares-0.0.7.tar.gz | 2.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autospares-0.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.4 kB
Release files / autospares-0.0.7.tar.gz
| Download URL | autospares-0.0.7.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b9256363c0cf1ea2601f7ed08b8bb680c7a0dd48a92e64eda20a09c8d87f456f
|
|
BLAKE2b-256 checksum How to use checksums |
ec6a58c6fada65acdc0b9aa1f37b5bf852114c89446618eee41a87c53c195e29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.5
|
Release files / autospares-0.0.7-py3-none-any.whl
| Download URL | autospares-0.0.7-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
99b357a92f6e575927b0181c0e049f27a2755e9b70e0f2dfd56baf7d9e60bc35
|
|
BLAKE2b-256 checksum How to use checksums |
c7503adc9aea8ccf9679e6d1bb6f7cd9f2dd6e6c8166fddc22465445c63e611b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.5
|
Security for autospares 0.0.7
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.
