ci: add security scanning workflow (npm audit, Trivy, SBOM)#63
Open
dogukandemirci-software-engineer wants to merge 1 commit into
Conversation
Introduces a dedicated security.yml GitHub Actions workflow with three security gates that were previously absent from the project: - npm-audit: runs `npm audit --audit-level=high` to catch HIGH/CRITICAL vulnerabilities in JavaScript dependencies - trivy-fs: Trivy filesystem scan for HIGH/CRITICAL CVEs; results are uploaded as SARIF to the GitHub Security tab for triage - sbom: generates a CycloneDX Software Bill of Materials artifact retained for 90 days for supply-chain compliance Adds .trivy.yaml to skip node_modules, dist, and coverage directories so scan output stays focused on source-level findings. The workflow triggers on push/PR and on a weekly cron schedule so that newly disclosed CVEs are caught between releases.
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
1 participant
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.
What
This PR introduces a dedicated
security.ymlGitHub Actions workflow that adds three security gates currently absent from the project.Why
The repository currently has no CI at all. Without automated dependency scanning, HIGH/CRITICAL CVEs in npm packages can silently reach production. This is a minimal, non-breaking addition that brings the project in line with supply-chain security best practices.
Changes
.github/workflows/security.yml— three parallel jobs:npm-auditnpm audittrivy-fssbom.trivy.yaml— Trivy config that skipsnode_modules/,dist/, andcoverage/to keep results focused on source-level findings.Trigger schedule: runs on every push/PR and weekly (Monday 08:00 UTC) so newly published CVEs are caught between releases.
Test plan
npm audit --audit-level=highexits 0 on current lockfile