The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for aih-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 | |
|---|---|---|---|---|
| aih_infra-0.0.1.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aih_infra-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.4 kB
Release files / aih_infra-0.0.1.tar.gz
| Download URL | aih_infra-0.0.1.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f91cba78e50ffeb08a1b4ecb71f6a26f582146618e79e8fc2f7af8660e15c9ce
|
|
BLAKE2b-256 checksum How to use checksums |
ffe8b31f8150529a073c921ea298dbb5e73dbf347fee7c49514fb7cc32b3853f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Release files / aih_infra-0.0.1-py3-none-any.whl
| Download URL | aih_infra-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4835ed3cadfac90db70f28ef913ae7dd133f12709debbcfe951c80331d377e0f
|
|
BLAKE2b-256 checksum How to use checksums |
05bddd5efa5a2bf3299608c96fd58fe3f1523629b7e3eea8f777f9bcea693f8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Security for aih-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.
