Skip to content

chore: add security scanning workflows - #12

Open
haribabug wants to merge 2 commits into
develop_deprecatedfrom
add-security-scanning
Open

haribabug wants to merge 2 commits into
develop_deprecatedfrom
add-security-scanning

Conversation

@haribabug

Copy link
Copy Markdown

Security Scanning Workflows Enablement

This PR adds standardized security scanning workflows and configurations from ROCm/rocm-repo-template.

Security Controls

  • PR Security Scan
  • Weekly Security Scan
  • Dependabot
  • CodeQL, Bandit, Gitleaks, Trivy, and Zizmor

Files added / updated

  • .github/workflows/pr-security-scan.yml — scans every pull request
  • .github/workflows/weekly-security-scan.yml — scheduled weekly scan
  • .github/dependabot.yml — automated dependency updates
  • .github/scan_tools_configs/bandit.yml — Python static analysis config
  • .github/scan_tools_configs/gitleaks.toml — secret detection config
  • .github/scan_tools_configs/trivy.yml — container/dependency vulnerability config
  • .github/scan_tools_configs/zizmor.yml — GitHub Actions security config

Why

This change aligns this repository with the ROCm GitHub Organization Security Baseline and enables consistent security controls across ROCm repositories.


For more details, refer ROCm GitHub Org Security Controls Baseline Architecture

Support/Questions: Teams Channel ROCm Security Discussions

@haribabug
haribabug requested a review from a team as a code owner September 29, 2026 20:54
@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.

@github-actions

github-actions Bot commented Oct 14, 2026 •

Copy link
Copy Markdown
Security scan found no critical or high findings on lines changed by this pull request (coverage incomplete)

Coverage was incomplete:

  • Security scan / Security scanners concluded with failure.

View the security scan run for complete reports.

“New” means the finding is located in a changed file on an added or modified line; it is not a base-versus-head findings delta.

Add the standardized security scanning workflows and tool configs from
ROCm/rocm-repo-template, aligning this repository with the ROCm GitHub
Organization Security Controls Baseline.

Workflows:
- .github/workflows/pr-security-scan.yml - scans every pull request
- .github/workflows/weekly-security-scan.yml - scheduled weekly scan
- .github/dependabot.yml - automated dependency updates

Tool configs under .github/scan_tools_configs/:
- bandit.yml - Python static analysis
- gitleaks.toml - secret detection
- trivy.yml - container and dependency vulnerabilities
- zizmor.yml - GitHub Actions security
@haribabug
haribabug force-pushed the add-security-scanning branch from 3a7447b to dda9a49 Compare October 14, 2026 13:19
Updates 8 security scanning file(s) to the latest version from
ROCm/rocm-repo-template.
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