1 maintainer
Metadata
1 maintainer
Release files for maibot-dashboard 1.9.1
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 | |
|---|---|---|---|---|
| maibot_dashboard-1.9.1.tar.gz | 3.1 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| maibot_dashboard-1.9.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.2 MB
Release files / maibot_dashboard-1.9.1.tar.gz
| Download URL | maibot_dashboard-1.9.1.tar.gz |
|---|---|
| Size | 3.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
529b6e1c7d97d6191367b81565eb1af58e9cce3203406f239b37c1907b723756
|
|
BLAKE2b-256 checksum How to use checksums |
4ea8ab2500013de42ae6866a9ffdcf97decaed7e6e3fa2d46b1e7dc12fdd8c28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / maibot_dashboard-1.9.1-py3-none-any.whl
| Download URL | maibot_dashboard-1.9.1-py3-none-any.whl |
|---|---|
| Size | 3.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
490a377cd3cd946bce460ee8cb1d423ebdeada2ff57a8f2bde239a7d334d3a28
|
|
BLAKE2b-256 checksum How to use checksums |
0c89c7758bec3d3d4aba658308ae7de1a1531d0d3069d4aea3652ede91b01578
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for maibot-dashboard 1.9.1
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.
