The author of this package has not provided a project description
Metadata
Release files for ivpm 2.2.0.19381256398
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.2.0.19381256398.tar.gz | 121.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ivpm-2.2.0.19381256398-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 196.9 kB
Release files / ivpm-2.2.0.19381256398.tar.gz
| Download URL | ivpm-2.2.0.19381256398.tar.gz |
|---|---|
| Size | 121.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a0aa19c2c51278fabed8213a31597dadb8d1d55786018fe06e5d131d85d77af3
|
|
BLAKE2b-256 checksum How to use checksums |
f0451cf2109bfa9364117ef6d5edcaa52b3aac20a124e090c4beb912b960ccaa
|
| 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.2.0.19381256398-py3-none-any.whl
| Download URL | ivpm-2.2.0.19381256398-py3-none-any.whl |
|---|---|
| Size | 75.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e9a5727ace59a6ed22ee61cf2bcc05d202c0f405402022a41aa9f234644650ba
|
|
BLAKE2b-256 checksum How to use checksums |
0dd30a2ed393c87abe587786cb45868fff9922419b51fcd725d6c58e775df370
|
| 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.2.0.19381256398
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.