The author of this package has not provided a project description
Metadata
Release files for ivpm 2.1.0.17362009160
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 | |
|---|---|---|---|---|
| ivpm-2.1.0.17362009160.tar.gz | 115.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ivpm-2.1.0.17362009160-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 186.4 kB
Release files / ivpm-2.1.0.17362009160.tar.gz
| Download URL | ivpm-2.1.0.17362009160.tar.gz |
|---|---|
| Size | 115.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea58b0b346ca74ab9c876f15eacaaa866239dcf16a166c6e064d75b8a2b75d91
|
|
BLAKE2b-256 checksum How to use checksums |
12fe386c85bd92c2238e12b9efdf139443b6f3b1eacc6dd4bd495e1595d5cf7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / ivpm-2.1.0.17362009160-py3-none-any.whl
| Download URL | ivpm-2.1.0.17362009160-py3-none-any.whl |
|---|---|
| Size | 71.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
358aeb9d05923697070f3472e0bf065d8d3b6ca7ce3a8c3c1d661ad7e7f533c0
|
|
BLAKE2b-256 checksum How to use checksums |
0f82a7493651a3bedc8ad8b93a2273c799fdcf7e74f42793259cebb4243cbd83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for ivpm 2.1.0.17362009160
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.