Automated dependency vulnerability#110
Open
gloskull wants to merge 2 commits into
Open
Conversation
…y-scanning-pipeline Add dependency vulnerability scanning workflow, runbook, and committed npm lockfiles
Contributor
|
resolve conflicts @gloskull |
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
2 participants
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.
Motivation
Introduce an automated, repository-wide dependency vulnerability scanning pipeline to block exploitable changes and enforce triage processes.
Provide reproducible Node.js audits by committing package-lock.json files for the meter-simulator and usage-dashboard projects.
Document operation, triage and rollout procedures so maintainers and security operators have a clear runbook.
Description
Add a new GitHub Actions workflow at .github/workflows/dependency-vulnerability-scan.yml with jobs for PR Dependency Review, Rust cargo audit, Node npm audit, a scheduled daily scan, and a summary enforcement step.
Commit meter-simulator/package-lock.json and usage-dashboard/package-lock.json so the workflow can run npm ci and npm audit deterministically from lockfiles.
Add docs/runbooks/DEPENDENCY_VULNERABILITY_SCANNING.md describing architecture, blocking policy, triage procedure, monitoring/alerting, and deployment strategy.
Update README.md CI/CD section to reference the new scanning workflow and runbook.
Testing
Validated the workflow YAML parses with ruby -e "require 'yaml'; YAML.load_file('.github/workflows/dependency-vulnerability-scan.yml')" which succeeded.
Ran npm ci --ignore-scripts in meter-simulator which succeeded to produce a reproducible lockfile.
Ran npm ci --ignore-scripts in usage-dashboard which succeeded to produce a reproducible lockfile.
Attempted npm audit --audit-level=moderate --omit=dev in both Node projects but the audit call failed in this environment due to the registry returning 403 Forbidden, so audits could not be completed locally (the workflow will run them in CI).
Closes #80