OWASP Zed Attack Proxy (ZAP) produces reports that are formatted in either `json` or `xml`. However, the format of the `xml` reports generated are not friendly to integrate with Jenkin's Junit plugin. This is normally what we would want to do if we want to perform ZAP scans as part of our CI/CD workflow.
## Usage
```python
import zap_report_formatter from zap_report_formatter
zap_report_formatter.format('path to ZAP json report', 'path to json whitelist file', 'output path of xml file')
```
Here is what the `json` whitelist file should be like:
```json
{
"42": {
"name": "Source Code Disclosure - SVN",
"regex_uris": [
"http://example.localhost"
],
"reason": "Reason."
}
}
```
1 maintainer
Metadata
1 maintainer
Release files for zap_report_formatter 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 | |
|---|---|---|---|---|
| zap_report_formatter-0.0.2.tar.gz | 2.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zap_report_formatter-0.0.2-py2.7.egg | Legacy Egg format | - | - | Details |
Total release size: 7.6 kB
Release files / zap_report_formatter-0.0.2.tar.gz
| Download URL | zap_report_formatter-0.0.2.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea2b794dcd9ab578a07ed58b7f0515c6968884ad4394f71a78564449c9e201ad
|
|
BLAKE2b-256 checksum How to use checksums |
a3de6c5b2f4b76373306b33b71c7f51b64e1f4449f3771339bdeeb7393374af5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Release files / zap_report_formatter-0.0.2-py2.7.egg
| Download URL | zap_report_formatter-0.0.2-py2.7.egg |
|---|---|
| Size | 5.0 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
f3bef58d52cd4de4cc63d7ce676ee639104923adcebe0b721d903958abc3bd06
|
|
BLAKE2b-256 checksum How to use checksums |
9a0631a446ed0915f0acd9f84e7afb7c64f67a9051f1c4bbb3013693eb813077
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Security for zap_report_formatter 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
