Share an OWASP ZAP report
A DAST scan produces a list of alerts and, immediately afterwards, a much more valuable list: which of them matter. The scan is automated. The second list is human, and CI has nowhere to put it — so the reasoning ends up in a Slack thread and is gone by the next scan, at which point someone triages the same alert again from scratch.
ZAP's HTML output is a single self-contained file. Give it a URL and the triage stops evaporating.
Publish it
zap-baseline.py -t https://staging.example.com -r zap.html || true
curl -fsS -X PATCH \
"https://commareports.com/api/v1/reports/$COMMA_REPORT_ID" \
-H "Authorization: Bearer $COMMA_API_TOKEN" \
-H "Content-Type: application/json" \
-d "$(jq -n --rawfile html zap.html \
--arg title "ZAP — staging — $(date +%F)" \
'{title: $title, html: $html}')"
|| true because zap-baseline.py exits non-zero when it finds warnings,
and that is precisely the run worth publishing. PATCH against a saved report
id keeps one URL per target with a revision per scan.
Use a scoped token with reports:write only, and keep
the report private or team-visible — see the
sharing model.