The author of this package has not provided a project description
Metadata
Release files for bd-map-plotter 0.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 | |
|---|---|---|---|---|
| bd_map_plotter-0.2.tar.gz | 1.6 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bd_map_plotter-0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.3 MB
Release files / bd_map_plotter-0.2.tar.gz
| Download URL | bd_map_plotter-0.2.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fbc4bdf4385e080f49ebb01a99a5da9383be7dcf80350af0e7b27bffe9c5d8ac
|
|
BLAKE2b-256 checksum How to use checksums |
2abb18a09ac72703d84bcfdd34aeea045338575d0d1187b50b14557eb8b4b154
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.2
|
Release files / bd_map_plotter-0.2-py3-none-any.whl
| Download URL | bd_map_plotter-0.2-py3-none-any.whl |
|---|---|
| Size | 1.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b08f127f50eb3e5b04dd9de7ca34a366790f9d8cf464a9a9eb9806c29bfe602
|
|
BLAKE2b-256 checksum How to use checksums |
978a9ac06d1b68c18a1ed7c5bf34090a73c489c565be507c31b8ab995f2cdef7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.2
|
Security for bd-map-plotter 0.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.