The author of this package has not provided a project description
Metadata
Release files for autogen-kya 0.1.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 | |
|---|---|---|---|---|
| autogen_kya-0.1.0.tar.gz | 10.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autogen_kya-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.7 kB
Release files / autogen_kya-0.1.0.tar.gz
| Download URL | autogen_kya-0.1.0.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
45c04c50356d68b6a8a2dc8189bc0d58087a98323b4343581d3df64a41044ef5
|
|
BLAKE2b-256 checksum How to use checksums |
9becc2c3f2b4092bf5e695769eee44d0880c49d3ef4fc1945d8fc58a08b00999
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.2
|
Release files / autogen_kya-0.1.0-py3-none-any.whl
| Download URL | autogen_kya-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
60e81be70165dea033f544b35954b19187f683624049f20e2c551f26bd17e34d
|
|
BLAKE2b-256 checksum How to use checksums |
912cc9fdf53d11d18ca1b48a0faaaafdf76f05c1241fa8cabbde29a373da1125
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.2
|
Security for autogen-kya 0.1.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.