Skip to content

build(ci): implement SCA pipeline with multi-tool vulnerability scanning#15

Draft
moghit-eou wants to merge 3 commits into
Medical-Informatics-Platform:masterfrom
moghit-eou:ci/sca-pipeline
Draft

build(ci): implement SCA pipeline with multi-tool vulnerability scanning#15
moghit-eou wants to merge 3 commits into
Medical-Informatics-Platform:masterfrom
moghit-eou:ci/sca-pipeline

Conversation

@moghit-eou

Copy link
Copy Markdown
Contributor

Summary

Implements the SCA CI pipeline using GitHub Actions and a Python glue script.

What's included

  • GitHub Actions workflow triggered on pull requests
  • Python script orchestrating multiple SCA tools (Trivy, osv-scanner, dependency-check)
  • Each tool outputs SARIF
  • SARIF results uploaded to GitHub Security tab

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

Trivy fetches Maven dependencies remotely when the local cache is empty,
which triggers a 429 rate limit from Maven Central and breaks the scan.
Pre-resolving with `mvn dependency:resolve` fills the local cache first,
so Trivy can scan without making external requests.

ci: migrate to Debian Trixie container
refactor: downrade python to 3.13

refactor(ci): move maven installation to setup script

Maven is not installed in the Debian Trixie container by default, which is required for SCA dependency resolution.

ci: cache Maven dependencies to fix Trivy 429 rate limit

Trivy fetches Maven BOM files directly from Maven Central when the locals
cache is empty, triggering a 429 rate limit block.

Added Maven dependency caching (~/.m2) using actions/cache, keyed on
pom.xml content hash. This ensures Maven Central is only hit when
dependencies actually change, and Trivy scans from local cache.
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