The author of this package has not provided a project description
Metadata
Release files for ivpm 2.3.0.19982430133
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.3.0.19982430133.tar.gz | 134.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ivpm-2.3.0.19982430133-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 218.5 kB
Release files / ivpm-2.3.0.19982430133.tar.gz
| Download URL | ivpm-2.3.0.19982430133.tar.gz |
|---|---|
| Size | 134.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2109047c12792c868fcc678ed1d23bfd17ffac8e5b179dd24133247d9da841c8
|
|
BLAKE2b-256 checksum How to use checksums |
ea155c283274f216c4e6a33f16f07299afea5f122bbb60e1839dd5723de0d179
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / ivpm-2.3.0.19982430133-py3-none-any.whl
| Download URL | ivpm-2.3.0.19982430133-py3-none-any.whl |
|---|---|
| Size | 84.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
599110095a737429f2d50cfa6f3dc74bf2a2d3615c9593bb43b25cea4a03b9b5
|
|
BLAKE2b-256 checksum How to use checksums |
b29e4622f91d5a7024def4df4737d12be4995db5a35c7fe4128c6df6f976fe11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for ivpm 2.3.0.19982430133
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.