The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for askai-cli 0.0.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 | |
|---|---|---|---|---|
| askai-cli-0.0.1.tar.gz | 5.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| askai_cli-0.0.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 10.5 kB
Release files / askai-cli-0.0.1.tar.gz
| Download URL | askai-cli-0.0.1.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b46ddc685ec22bb85cab4aa7e4155e580a21f57ce8373b5406e04eb0111a0fde
|
|
BLAKE2b-256 checksum How to use checksums |
6107001b0128d2761dc876c959d1876cf99e4c66a556ee736cc42b917c61e293
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / askai_cli-0.0.1-py2.py3-none-any.whl
| Download URL | askai_cli-0.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
3e3f046366d2f246ea5d21a76ef721616febc722920f319640c9edb2d1dbf039
|
|
BLAKE2b-256 checksum How to use checksums |
dacae76f952c949a28d0900541733f012bfcb1c9c1a52890cc8b69195bdabf6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for askai-cli 0.0.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.
