The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for xornlpcrack 0.1.2
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 | |
|---|---|---|---|---|
| xornlpcrack-0.1.2.tar.gz | 5.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xornlpcrack-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.9 kB
Release files / xornlpcrack-0.1.2.tar.gz
| Download URL | xornlpcrack-0.1.2.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf87a4500982c7e848de9215865920a4de614ce59a09b1d786d316b119683f91
|
|
BLAKE2b-256 checksum How to use checksums |
d75e4ebeaff862cb41be495f2ae2df7a3920158f2df94a40943f3967014e11f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.0
|
Release files / xornlpcrack-0.1.2-py3-none-any.whl
| Download URL | xornlpcrack-0.1.2-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dc339414bae9ad2c86795901020687aaad92fe20bad91ee8ca2b3c968aa57e60
|
|
BLAKE2b-256 checksum How to use checksums |
6a280695a9daff99719ac7e9fc29756acdc979c6dfd7c49e5d789e2cf79417a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.0
|
Security for xornlpcrack 0.1.2
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.
