The author of this package has not provided a project description
Metadata
Release files for ivpm 2.3.0.20604865452
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.20604865452.tar.gz | 245.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ivpm-2.3.0.20604865452-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 343.4 kB
Release files / ivpm-2.3.0.20604865452.tar.gz
| Download URL | ivpm-2.3.0.20604865452.tar.gz |
|---|---|
| Size | 245.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5dd6446793792d0d34ef8865fa6b7486afa77ae55abb625c291064f8591cc441
|
|
BLAKE2b-256 checksum How to use checksums |
be535c020c2094fc710240ca3d0dac123e0178ee0a606dd64fa052c389410a45
|
| 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.20604865452-py3-none-any.whl
| Download URL | ivpm-2.3.0.20604865452-py3-none-any.whl |
|---|---|
| Size | 97.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cf781d909dbbfda4368bc2fe21a567597fad4704610733d04987eb670108ba0a
|
|
BLAKE2b-256 checksum How to use checksums |
a4cd7aafcad2be0cea244df679ae69e1b6d38b1f393e017eeac24df2166640e7
|
| 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.20604865452
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.