1 maintainer
Metadata
1 maintainer
Release files for ai-error-handler 0.1.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 | |
|---|---|---|---|---|
| ai_error_handler-0.1.1.tar.gz | 3.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ai_error_handler-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.7 kB
Release files / ai_error_handler-0.1.1.tar.gz
| Download URL | ai_error_handler-0.1.1.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3ef6dcf459556a960d9c91952d2f1dcb271f3aaf99c85840d3536d4f33decf7
|
|
BLAKE2b-256 checksum How to use checksums |
9bf94bdbf0bf568a286480cdf9c9b4a18430680396b29fb9e6a1614f33401a82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.1
|
Release files / ai_error_handler-0.1.1-py3-none-any.whl
| Download URL | ai_error_handler-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c4a1e343b4d406eceb567d8f1cba04c0a06850ddc43db7cc52fd416e2f0f008a
|
|
BLAKE2b-256 checksum How to use checksums |
d7d74aa90c7297c873562b88bfafc74d92fd576dc2d53a1f7b604da520a99ffb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.1
|
Security for ai-error-handler 0.1.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.
