The author of this package has not provided a project description
Metadata
Release files for ivpm 2.3.0.20605022847
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.20605022847.tar.gz | 247.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ivpm-2.3.0.20605022847-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 344.6 kB
Release files / ivpm-2.3.0.20605022847.tar.gz
| Download URL | ivpm-2.3.0.20605022847.tar.gz |
|---|---|
| Size | 247.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c64c67c259b1ff6d6fc98ec11f3bef444e8daf520951e4bf3a3871fd2d28ff08
|
|
BLAKE2b-256 checksum How to use checksums |
bf99f85c765b3a42f6c1e78b2042f24405134ec336a7f1950c1a9f48f23062eb
|
| 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.20605022847-py3-none-any.whl
| Download URL | ivpm-2.3.0.20605022847-py3-none-any.whl |
|---|---|
| Size | 97.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed1116ba633670168c07648be74e3b84c3dc21e9235e99b5f9da3ab9f9599a3a
|
|
BLAKE2b-256 checksum How to use checksums |
a41882fe0e7961d0a99e6c431f8ca29b4d36d2b7a246f1de56f27a6088c50848
|
| 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.20605022847
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.