The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pypomes-iam 1.1.0
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 | |
|---|---|---|---|---|
| pypomes_iam-1.1.0.tar.gz | 22.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pypomes_iam-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 48.7 kB
Release files / pypomes_iam-1.1.0.tar.gz
| Download URL | pypomes_iam-1.1.0.tar.gz |
|---|---|
| Size | 22.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
067714a60ae12b98eeeb985e42ad2b07d276068f40904107b0dd4fedf0559aa5
|
|
BLAKE2b-256 checksum How to use checksums |
c09d39978767886b22d9891feb0d950aa4195bbf582c2135ea914d36c5c0ec26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Release files / pypomes_iam-1.1.0-py3-none-any.whl
| Download URL | pypomes_iam-1.1.0-py3-none-any.whl |
|---|---|
| Size | 26.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
870824ce01d03847c6d7476184b64a5f144af4c09ebd652dea7edae35aba05cb
|
|
BLAKE2b-256 checksum How to use checksums |
981e1b151c98e989eec568bb4a9fdde70295d3fc317e16e41266a49b113e38a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Security for pypomes-iam 1.1.0
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.
