Skip to content

ci(security): Add the org vulnerability scan workflow - #1894

Merged
yahyafakhroji merged 1 commit into
mainfrom
fix/dependency-vulnerabilities
Nov 18, 2026
Merged

yahyafakhroji merged 1 commit into
mainfrom
fix/dependency-vulnerabilities

Conversation

@yahyafakhroji

Copy link
Copy Markdown
Contributor

Problem
quality-checks runs npm audit and fails only on high severity, so medium and low advisories in the site's dependencies never fail a build.

Solution
A new workflow runs the shared datum-cloud/actions vuln-scan, which checks the lockfile against OSV at every severity, on pull requests, pushes to main, every Monday and on demand. The current lockfile scans clean, so there is no ignore file. The audit gate stays as it is.

Run the shared datum-cloud osv-scanner workflow on pull requests, main,
a weekly schedule and manual dispatch. It complements the npm audit gate
in quality-checks, which only fails on high severity.
@yahyafakhroji
yahyafakhroji requested a review from a team as a code owner November 18, 2026 22:52
@yahyafakhroji
yahyafakhroji merged commit 4dfc09f into main Nov 18, 2026
9 checks passed
@yahyafakhroji
yahyafakhroji deleted the fix/dependency-vulnerabilities branch November 18, 2026 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants