Burp-UI Meta package for monitor requirements
Metadata
Release files for burp-ui-monitor 1.1.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 | |
|---|---|---|---|---|
| burp-ui-monitor-1.1.1.tar.gz | 99.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| burp_ui_monitor-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 211.0 kB
Release files / burp-ui-monitor-1.1.1.tar.gz
| Download URL | burp-ui-monitor-1.1.1.tar.gz |
|---|---|
| Size | 99.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
26558a35c68b5c95e7b247dccb449167d3f0a58e98c927baa430add209e1f602
|
|
BLAKE2b-256 checksum How to use checksums |
6181dbfa4dd3f93486ce15b17f178084bf7f84dba94aeaead1a6fa8a9186b174
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.15
|
Release files / burp_ui_monitor-1.1.1-py3-none-any.whl
| Download URL | burp_ui_monitor-1.1.1-py3-none-any.whl |
|---|---|
| Size | 111.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
da4a1d554c52cc3a7fe742d66b91ab34e424fb5a663d9635f03a67264bdc56e7
|
|
BLAKE2b-256 checksum How to use checksums |
71b57d7ae037801682d604c10b9abe6a5d4a0c9edb5a1d63fcc1857046be5624
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.15
|
Security for burp-ui-monitor 1.1.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.