The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mappr 0.5.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 | |
|---|---|---|---|---|
| mappr-0.5.2.tar.gz | 13.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mappr-0.5.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.1 kB
Release files / mappr-0.5.2.tar.gz
| Download URL | mappr-0.5.2.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f16df4ad14b9a444cb81b14d492b3379c8e5331e884b3c86214cf5221d70d472
|
|
BLAKE2b-256 checksum How to use checksums |
87761535578457b2f2d74b7b2f86cd905f3c990556772bd3e3dc98381fc53973
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.16
|
Release files / mappr-0.5.2-py3-none-any.whl
| Download URL | mappr-0.5.2-py3-none-any.whl |
|---|---|
| Size | 13.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7c48b35c4a7a09c655be7f2e7ef63f2d64bf0d4412f7f075398d1e8677beb5e0
|
|
BLAKE2b-256 checksum How to use checksums |
900aef6de9ec7f70beba5bd91a71201f3713748a26272a3e0a5cf7c622f01879
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.16
|
Security for mappr 0.5.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.
