A Streamlit WebUI application for the mflux project.
Metadata
Release files for mflux-streamlit 0.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 | |
|---|---|---|---|---|
| mflux_streamlit-0.0.2.tar.gz | 8.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mflux_streamlit-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.6 kB
Release files / mflux_streamlit-0.0.2.tar.gz
| Download URL | mflux_streamlit-0.0.2.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9080a49a13e049fe0dbbf012f4b5475dc165ab1c9871a8a859713dbc0e228abf
|
|
BLAKE2b-256 checksum How to use checksums |
7be2ecbc1e620be1f54939d196a3095ac7f7763b37d72a5f1f42806c1f177f65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Release files / mflux_streamlit-0.0.2-py3-none-any.whl
| Download URL | mflux_streamlit-0.0.2-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7397cd043852f4afbcb0fbd2c81e056e9ab8a73733ce2974e13e03e46f2cb9f3
|
|
BLAKE2b-256 checksum How to use checksums |
6b8e4f50481e2f9ff06046d5a6acd9fd19faa48c83edd0fdd0a7d8d2d80248cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Security for mflux-streamlit 0.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.