The author of this package has not provided a project description
Metadata
Release files for ivpm 2.3.0.20644774837
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.20644774837.tar.gz | 247.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ivpm-2.3.0.20644774837-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 345.2 kB
Release files / ivpm-2.3.0.20644774837.tar.gz
| Download URL | ivpm-2.3.0.20644774837.tar.gz |
|---|---|
| Size | 247.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9536d67268ca55d6aadc5aa7f66356876d007d68e233d4a71bc47a193350ba17
|
|
BLAKE2b-256 checksum How to use checksums |
ba86b05f846c41cf188bd23b3013b1c37e94760fa0c2208d89786ad88355963e
|
| 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.20644774837-py3-none-any.whl
| Download URL | ivpm-2.3.0.20644774837-py3-none-any.whl |
|---|---|
| Size | 97.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d5e6c15b7f703418b2dde081d31f0026052b13419e55da7269ac7957ebdc6443
|
|
BLAKE2b-256 checksum How to use checksums |
b2aaf030e7208649347f839fc699d91afeae991bc0582e6c420a9d1d71f78b7a
|
| 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.20644774837
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.