Skip to content

chore: migrate from Trivy to Grype for vulnerability scanning#381

Open
JAORMX wants to merge 1 commit intomainfrom
chore/migrate-trivy-to-grype
Open

chore: migrate from Trivy to Grype for vulnerability scanning#381
JAORMX wants to merge 1 commit intomainfrom
chore/migrate-trivy-to-grype

Conversation

@JAORMX
Copy link
Collaborator

@JAORMX JAORMX commented Mar 20, 2026

Summary

  • Replace aquasecurity/trivy-action with anchore/scan-action (Grype) v7.3.2
  • Rename trivy.yml to security-scan.yml
  • Drop secret scanning (not supported by Grype)
  • Update SARIF upload to reference Grype output

Test plan

  • Verify Grype scan runs successfully in CI
  • Check SARIF results appear in Security tab

🤖 Generated with Claude Code

Replace aquasecurity/trivy-action with anchore/scan-action (Grype) v7.3.2.
Rename trivy.yml to security-scan.yml. Drop secret scanning.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@JAORMX JAORMX force-pushed the chore/migrate-trivy-to-grype branch from f475244 to 0387e70 Compare March 20, 2026 09:22
@github-advanced-security
Copy link

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.

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.

1 participant