The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for ailabcode 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 | |
|---|---|---|---|---|
| ailabcode-1.0.0.tar.gz | 3.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ailabcode-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.6 kB
Release files / ailabcode-1.0.0.tar.gz
| Download URL | ailabcode-1.0.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a54b4a7767d3ec71424e3615a70bab8e093564bab88515c991788a5957fa939
|
|
BLAKE2b-256 checksum How to use checksums |
78f75a529895d7ea2d0b45ede21f689033a6af69a78f4f2c0ec547c4f9800e95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / ailabcode-1.0.0-py3-none-any.whl
| Download URL | ailabcode-1.0.0-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1cf1a0772457e659bc2797e19e1c8547e7ff5347b41c9644d8e73fedb55fd36
|
|
BLAKE2b-256 checksum How to use checksums |
71667deedb2a804bd945f388d3b233a2cccae59c67821d29bae331b998290c97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for ailabcode 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.
