The author of this package has not provided a project description
Metadata
Release files for ivpm 2.6.0.22971066477
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.6.0.22971066477.tar.gz | 325.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ivpm-2.6.0.22971066477-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 470.9 kB
Release files / ivpm-2.6.0.22971066477.tar.gz
| Download URL | ivpm-2.6.0.22971066477.tar.gz |
|---|---|
| Size | 325.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e2f573989479278a1f72a02a6e62620ca0b961cf08c4632152ad93623a55313
|
|
BLAKE2b-256 checksum How to use checksums |
30bdcfb0e96362df716175d42772ab779ad8543040889f9b3ba39cc1bd79af8b
|
| 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.6.0.22971066477-py3-none-any.whl
| Download URL | ivpm-2.6.0.22971066477-py3-none-any.whl |
|---|---|
| Size | 145.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fee16e7353835dc4e19715ade3b1b6b28f54b1349c38bb099d9102b57b6e1e5c
|
|
BLAKE2b-256 checksum How to use checksums |
d861d2de42a795f615cb7b2a03a2747e19733cd65b4d6a57299eb5042843ec33
|
| 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.6.0.22971066477
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.