The author of this package has not provided a project description
Metadata
Release files for iminfra 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 | |
|---|---|---|---|---|
| iminfra-0.1.0.tar.gz | 1.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iminfra-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.2 kB
Release files / iminfra-0.1.0.tar.gz
| Download URL | iminfra-0.1.0.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bdc622ba806842e638096c57a282fb185fd9ee034778e7f1e377e908e231e096
|
|
BLAKE2b-256 checksum How to use checksums |
cd07857fa4de33dc823cb8a8727cf0ec35d3e3eec9836568bfb44871c307c8b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.12 CPython/3.10.1 Linux/5.16.2-1-MANJARO
|
Release files / iminfra-0.1.0-py3-none-any.whl
| Download URL | iminfra-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
72abcfd1800a0cdc152dc7b64abda35e3cc70af4c525e9371d23204c582fca98
|
|
BLAKE2b-256 checksum How to use checksums |
7ba209992502038ace17e802609e50429c3e267d5585f508fec504937d560d65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.12 CPython/3.10.1 Linux/5.16.2-1-MANJARO
|
Security for iminfra 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.