Add OWASP ZAP baseline scan workflow#1146
Draft
murderteeth wants to merge 1 commit into
Draft
Conversation
Runs weekly on Monday mornings and on manual trigger. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Dependency ReviewThe following issues were found:
Snapshot WarningsEnsure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice. License Issues.github/workflows/zap-baseline.yml
OpenSSF Scorecard
Scanned Files
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a GitHub Actions workflow that runs an OWASP ZAP baseline scan against the site. ZAP is an open-source web security scanner maintained by OWASP — the baseline scan passively crawls the target and checks for common security issues like missing headers (CSP, clickjacking, HSTS), insecure cookies, information leaks, mixed content, and other OWASP Top 10 surface-level findings. Running it regularly helps catch security regressions before they hit production, without needing a full pentest.
Runs weekly on Monday mornings and can be triggered manually via
workflow_dispatch. Includes.gitignoreentries for local scan artifacts and a README section on running the scan locally withact.How to review
zap-baseline.ymlis the whole workflow — 26 lines.gitignoreandREADME.mdchanges are supporting housekeepingTest plan
act workflow_dispatch— scan completed with 57 passes, 10 info-level warnings, 0 failuresRisk / impact
None — passive scan only, no effect on existing CI or deployments.