1 maintainer
Metadata
1 maintainer
Release files for xmanual 0.5
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 | |
|---|---|---|---|---|
| xmanual-0.5.tar.gz | 9.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xmanual-0.5-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 19.3 kB
Release files / xmanual-0.5.tar.gz
| Download URL | xmanual-0.5.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0451087b63bbde44c576a19909b1c8432ca80697f56c310b64a2074f7c7b950b
|
|
BLAKE2b-256 checksum How to use checksums |
9777b35a8b0c20f7cffc15d6ded206ab6a93a91c7b9a87710b49a31a8b9a7683
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / xmanual-0.5-py2.py3-none-any.whl
| Download URL | xmanual-0.5-py2.py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
3f715ec45d788584a3638c1730bc0bea94edefde0735e432efae400824a9b933
|
|
BLAKE2b-256 checksum How to use checksums |
cf7b280f120cb578920821cecde12571f6d65c2cc4fa7ccb7e19d42af3ae9696
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for xmanual 0.5
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.
