The author of this package has not provided a project description
Metadata
Release files for pretty-match 0.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 | |
|---|---|---|---|---|
| pretty_match-0.1.0.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pretty_match-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.1 kB
Release files / pretty_match-0.1.0.tar.gz
| Download URL | pretty_match-0.1.0.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6acff343e9ab81539224d4b1eab048b904e47ea74e6ec44b04d6300bd7f43f97
|
|
BLAKE2b-256 checksum How to use checksums |
fbb2e1671f73f1db6c3253c9b3b11457dc989aa983373607e634c55f5b283cb7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.10 CPython/3.10.5 Linux/5.13.0-1031-azure
|
Release files / pretty_match-0.1.0-py3-none-any.whl
| Download URL | pretty_match-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
205df31873b6457d5cb27e4c971648b89ec47aac83aa7ddbe9dfe568a6607df0
|
|
BLAKE2b-256 checksum How to use checksums |
4188dabebd1ff9d8874c4d1529beec8cca19332ca5d0b618450a8a3e7ee14cc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.10 CPython/3.10.5 Linux/5.13.0-1031-azure
|
Security for pretty-match 0.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.