This is the home page of our project.
1 maintainer
Metadata
1 maintainer
Release files for moshpdfbybii 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 | |
|---|---|---|---|---|
| moshpdfbybii-1.0.tar.gz | 13.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| moshpdfbybii-1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.7 kB
Release files / moshpdfbybii-1.0.tar.gz
| Download URL | moshpdfbybii-1.0.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5e6fc4228ca5e8e38a34a20374162dc46824da62d2450634862601ff7f05c9e2
|
|
BLAKE2b-256 checksum How to use checksums |
e169d5586329a24c93a8e928beeaf4aa7daae81f7b8b18e4c3b9ecf2774bd38a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.2
|
Release files / moshpdfbybii-1.0-py3-none-any.whl
| Download URL | moshpdfbybii-1.0-py3-none-any.whl |
|---|---|
| Size | 14.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
96d4bce20487ee4c666e61815acec0d3b21aa216d637f5b07609d9ff92994a3d
|
|
BLAKE2b-256 checksum How to use checksums |
14b72e348dfa87bc7d389d0b4a067dfde2cb2fc3415d58fcc07cf4e6dfd4f3cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.2
|
Security for moshpdfbybii 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.
