Skip to content

ci(security): Add the org vulnerability scan for npm - #240

Merged
ecv merged 1 commit into
datum-cloud:mainfrom
yahyafakhroji:fix/dependency-vulnerabilities
Nov 19, 2026
Merged

ecv merged 1 commit into
datum-cloud:mainfrom
yahyafakhroji:fix/dependency-vulnerabilities

Conversation

@yahyafakhroji

Copy link
Copy Markdown
Contributor

Problem
No CI job scanned the npm lockfiles in ui/ and ui/packaging/dmg against advisory databases.

Solution
A new workflow runs the shared datum-cloud/actions vuln-scan for npm on pull requests, pushes to main and every Monday. The npm lockfiles scan clean today. The root Cargo.lock has 42 RustSec advisories across 30 crates, and some need major bumps, so the scan leaves Rust out until a separate change fixes them.

Run the shared datum-cloud vuln-scan workflow on pull requests, main,
weekly, and on demand. Scope it to npm lockfiles; open Cargo advisories
need separate dependency bumps.
@yahyafakhroji
yahyafakhroji requested a review from a team as a code owner November 18, 2026 23:17

@ecv ecv left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve.

Adds the org vulnerability scan at datum-cloud/actions v1.29.0 for node, on pull requests, pushes to main and a weekly run. It passes here. The red set-month check is the project iteration job, unrelated.

@ecv
ecv merged commit 63a2856 into datum-cloud:main Nov 19, 2026
7 of 8 checks passed
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