Skip to content

Security: Add Automated Dependency Vulnerability Scanning in CI/CD Pipeline #517

Description

@Smartdevs17

Context

Supply chain attacks via vulnerable dependencies are an increasing threat. The project uses many npm, Rust, and Solidity packages.

Current Limitation/Problem

There is no automated dependency vulnerability scanning. Vulnerable transitive dependencies can go undetected for months. No policy for vulnerability remediation SLAs.

Expected Outcome

Automated vulnerability scanning for all dependency types (npm, Cargo, Solidity) in CI/CD, with configurable severity thresholds and policy-based blocking.

Acceptance Criteria

  • Integrate npm audit, Snyk or Dependabot for npm packages
  • Integrate cargo audit for Rust/Soroban dependencies
  • Parse vulnerability reports and fail CI on high/critical severity
  • Generate vulnerability report as CI artifact
  • Weekly scheduled scan (not just on PR)
  • Alert Slack/email on new critical vulnerabilities
  • Auto-create GitHub issue for vulnerabilities with severity and remediation
  • Dependency license compliance check
  • Policy configuration: which severities block CI, SLA for remediation
  • Dashboard: vulnerability trend over time

Technical Scope

  • .github/workflows/dependency-scan.yml - CI workflow
  • GitHub Dependabot configuration (auto-PRs for updates)
  • Custom script for aggregating scan results from multiple tools
  • Slack/notification integration for alerts
  • Prisma: VulnerabilityReport, DependencyVulnerability models
  • Edge cases: false positives, unmaintained packages, version conflicts

Metadata

Metadata

Assignees

Labels

200-points200 point issueStellar WaveIssues in the Stellar wave programdrips-waveIssues in the Drips Wave programhighHigh complexity issue

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions