Skip to content

Remove Trivy (compromised supply chain) #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jdfalk merged 1 commit into from
Mar 28, 2026
Merged

Remove Trivy (compromised supply chain) #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions .github/agents/Security Scanner Coordinator.agent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,6 @@ purpose:
- Coordinate SAST (static) and DAST (dynamic) security testing tools.
- Run language-specific security scanners (bandit, gosec, cargo-audit, npm audit).
- Scan for hardcoded secrets using truffleHog, gitleaks, or GitHub secret scanning.
- Perform container image vulnerability scanning with Trivy or Grype.
- Check security headers and HTTPS configuration for web applications.
- Generate unified security reports aggregating findings from multiple tools.
- Prioritize vulnerabilities by exploitability and impact (CVSS scores).
Expand Down Expand Up @@ -82,7 +81,6 @@ style-alignment:
- Security Instructions: CVE prioritization, CVSS scoring, responsible disclosure.
- SAST tools: bandit (Python), gosec (Go), cargo-audit (Rust), eslint-plugin-security (JS).
- Secret scanning: truffleHog/gitleaks for git history, fail CI on secret detection.
- Container scanning: Trivy or Grype with --severity HIGH, scan on build and schedule.
- DAST: OWASP ZAP or similar for web applications, test in staging environment.
- Reporting: SARIF for GitHub integration, JSON for programmatic processing, HTML for stakeholders.
- Remediation: Prioritize by CVSS score, availability of fix, and exposure risk.
Expand Down
4 changes: 0 additions & 4 deletions .github/linters/super-linter.env
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,8 +213,6 @@ VALIDATE_TERRAFORM_TERRASCAN=false
# Terragrunt
VALIDATE_TERRAGRUNT=false

# Trivy (Security scanner)
VALIDATE_TRIVY=false

# TypeScript
VALIDATE_TSX=true
Expand Down Expand Up @@ -498,8 +496,6 @@ GROOVY_LOG_LEVEL=info
# TERRAFORM_TERRASCAN_CONFIG_FILE=terrascan.toml
# TERRAFORM_TFLINT_CONFIG_FILE=.tflint.hcl

# Trivy
# TRIVY_CONFIG_FILE=trivy.yaml

# TypeScript
# TYPESCRIPT_ES_CONFIG_FILE=eslint.config.mjs
Expand Down
1 change: 0 additions & 1 deletion .github/security-guidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,6 @@ permissions:
**Recommended Actions**:

- CodeQL for code analysis
- Trivy for vulnerability scanning
- GitLeaks for secret detection

### 2. Dynamic Analysis
Expand Down