testland/zap-baseline
Configures and runs OWASP ZAP baseline scanning: `zap-baseline.py` Docker-packaged spider + passive scan suitable for CI gating; supports `-t target_url` + `-r html_report` + `-c config_file` rule customization (INFO/IGNORE/FAIL warnings) and Ajax spider via `-j` for JS-heavy SPAs; `zap-full-scan.py` active companion for staging. Covers authenticated scans end to end as a reference - ZAP Context, auth methods (form/JSON/script/browser), session management, verification strategy, OAuth/bearer injection, context XML export for `-n` - plus DAST cadence planning (PR-blocking passive baseline, nightly ZAP full + nuclei active layer, baseline-finding ratchet for legacy apps). Use when the user runs OWASP ZAP for pre-prod web app DAST, needs coverage of routes behind a login wall, or is designing a team's DAST rollout cadence.
73
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
SKILL.md’s required workflow runs OWASP ZAP baseline/spider against a user-supplied target via `zap-baseline.py -t URL`/`-n context.xml`, which causes ZAP at runtime to read free-text content from that (outsider-authored) web application as it crawls and passively scans pages.
Where we found it
user-supplied target web application (crawled by ZAP spider)
content-type · 13 sites
The plugin instructs ZAP to spider and passively/actively scan a user-supplied target web application, reading and processing all free-text content (HTML, JS, headers) from pages on that outsider-authored site.
W012: Unverifiable external dependency detected (runtime URL that controls agent).
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
The skill instructs runtime pulls/execution of remote artifacts (the container image "ghcr.io/zaproxy/zaproxy:stable" and GitHub Actions "zaproxy/action-baseline@v0.13.0" and "zaproxy/action-full-scan@v0.13.0") which are fetched at runtime and will execute remote code, so they constitute required external runtime dependencies.
Where we found it
ghcr.io/zaproxy/zaproxy:stable
dependency · 7 sites
The plugin instructs pulling and running the ghcr.io/zaproxy/zaproxy:stable Docker container image at runtime, which fetches and executes remote code.
zaproxy/action-baseline@v0.13.0
dependency · 2 sites
The plugin instructs using the zaproxy/action-baseline@v0.13.0 GitHub Action, which is fetched and executed at runtime from GitHub's action registry.
SKILL.md
178
- uses: zaproxy/action-baseline@v0.13.0
references/cadence.md
95
- uses: zaproxy/action-baseline@v0.13.0
zaproxy/action-full-scan@v0.13.0
dependency · 1 site
The plugin instructs using the zaproxy/action-full-scan@v0.13.0 GitHub Action, which is fetched and executed at runtime from GitHub's action registry.
references/cadence.md
114
- uses: zaproxy/action-full-scan@v0.13.0
- Audited
- Security analysis