The author of this package has not provided a project description
Metadata
Release files for aiappstore 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 | |
|---|---|---|---|---|
| aiappstore-0.1.0.tar.gz | 854 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aiappstore-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 kB
Release files / aiappstore-0.1.0.tar.gz
| Download URL | aiappstore-0.1.0.tar.gz |
|---|---|
| Size | 854 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
df471cce724b3403dab1312ae368151d1626c68428ac66733b5cf5f7afb8ea44
|
|
BLAKE2b-256 checksum How to use checksums |
92846024f7afc96d12f19b22173bcafde0cf404ce4a9af09874f7d4cd2562188
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.1
|
Release files / aiappstore-0.1.0-py3-none-any.whl
| Download URL | aiappstore-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a6c4e17d2b82a9d249a32be5a3006f22266e845b5cec39e5e38c0f36af44dbe
|
|
BLAKE2b-256 checksum How to use checksums |
ce3ce35e4cb4423a6aa92b761ec0f229028cd5ec722835678ddcbbc8e4711a25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.1
|
Security for aiappstore 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.