Repository navigation
ci(security): Add the org vulnerability scan workflow - #1894
Merged
Merged
Conversation
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.
scotwells
approved these changes
Nov 18, 2026
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.
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.