Metadata
Release files for ai4h-infra 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 | |
|---|---|---|---|---|
| ai4h_infra-0.0.1.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ai4h_infra-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 kB
Release files / ai4h_infra-0.0.1.tar.gz
| Download URL | ai4h_infra-0.0.1.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f0100b55bac2976e544cba1914913f3897d1f8d07d94cd5e9806c1f34312277
|
|
BLAKE2b-256 checksum How to use checksums |
74f1e1c368244a59b56f692a2f29b5bf66b615bae96501f90ebc8c33d1dbeae3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / ai4h_infra-0.0.1-py3-none-any.whl
| Download URL | ai4h_infra-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
954b46b0f5f48a5c3d5e1e092afb9c67f2cfcd40d08be6be6fad956d6440dfc0
|
|
BLAKE2b-256 checksum How to use checksums |
d2351e4bdac876e57b69eb8c1027335fed9459fd69946ca8e04c118d77990c05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for ai4h-infra 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.