The author of this package has not provided a project description
Metadata
Release files for ivpm 2.3.0.20013432165
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.20013432165.tar.gz | 143.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ivpm-2.3.0.20013432165-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 239.8 kB
Release files / ivpm-2.3.0.20013432165.tar.gz
| Download URL | ivpm-2.3.0.20013432165.tar.gz |
|---|---|
| Size | 143.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8ed87e52f9410e1d4841bf1e5b66f75538f8a841879140ef220de47f1b19246
|
|
BLAKE2b-256 checksum How to use checksums |
a10b9704f5b45858818b56ddfef90551d8922cedca73552a2cc9dc3f67c1b203
|
| 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.20013432165-py3-none-any.whl
| Download URL | ivpm-2.3.0.20013432165-py3-none-any.whl |
|---|---|
| Size | 95.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
28494eb337742614ae11aca7fecf4bb9cfbd37bc03e53417c85bba7a7060149a
|
|
BLAKE2b-256 checksum How to use checksums |
abd1315f5a60a3152a30f81fcad6e96a7d44262621ccf2c313cf329ea7f7fd07
|
| 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.20013432165
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.