This version still in development
1 maintainer
Metadata
1 maintainer
Release files for avtocod 1.0.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 | |
|---|---|---|---|---|
| avtocod-1.0.0.tar.gz | 23.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| avtocod-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 64.7 kB
Release files / avtocod-1.0.0.tar.gz
| Download URL | avtocod-1.0.0.tar.gz |
|---|---|
| Size | 23.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
954b3efc70599db97d112559b50efcb6073f6b1a9e0425f78910abbaa7c77865
|
|
BLAKE2b-256 checksum How to use checksums |
11482c8a3ceaafef2440a1c4590b0dc28398843f8b76a5cb317511538bd26ea0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.14 CPython/3.10.5 Linux/5.18.10-arch1-1
|
Release files / avtocod-1.0.0-py3-none-any.whl
| Download URL | avtocod-1.0.0-py3-none-any.whl |
|---|---|
| Size | 41.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cd5500f01d86a99923e97440a2843fd05b1f0b65c721fbb88ddb5da17bd559bf
|
|
BLAKE2b-256 checksum How to use checksums |
04fd9a06a868fbadd3442224c2fd91041589e87d77f7157831c1227004ff6860
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.14 CPython/3.10.5 Linux/5.18.10-arch1-1
|
Security for avtocod 1.0.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.
