fix: nuke trivy after compromise BED-7720

[rvazarkar]

Description

Motivation and Context

https://specterops.atlassian.net/browse/BED-7720

How Has This Been Tested?

No tests needed

Screenshots (if appropriate):

Types of changes

• Chore (a change that does not modify the application functionality)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• Documentation updates are needed, and have been made accordingly.
• I have added and/or updated tests to cover my changes.
• All new and existing tests passed.
• My changes include a database migration.

Summary by CodeRabbit

• Chores
  • Removed the automated vulnerability scanning workflow from the continuous integration pipeline.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6c2f7917-1741-4f10-ab33-ca4322592b4d

📥 Commits

Reviewing files that changed from the base of the PR and between 46046ef and cfc9a82.

📒 Files selected for processing (1)

• .github/workflows/vuln-scan.yml

💤 Files with no reviewable changes (1)

• .github/workflows/vuln-scan.yml

---

Walkthrough

A GitHub Actions workflow file for Trivy vulnerability scanning has been removed. The workflow previously executed on pull requests targeting release branches and performed repository-wide vulnerability scans with severity filtering for critical and high-severity issues.

Changes

Cohort / File(s)	Summary
Workflow Deletion .github/workflows/vuln-scan.yml	Removed GitHub Actions workflow that performed Trivy-based vulnerability scanning on pull requests targeting branch pattern *.*, including job configuration for repository scanning with CRITICAL and HIGH severity filtering.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A scan has ceased its nightly guard,
No more does Trivy work so hard,
The workflow file has taken flight,
Twenty-nine lines fade to night! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete with missing details. The Description section is empty, and Motivation/Context only provides a Jira link without explanation. Testing section states 'No tests needed' without justification.	Add a detailed description of changes (removing Trivy workflow), explain the security context of BED-7720, and clarify why testing is unnecessary for this chore.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: removing the Trivy vulnerability scanner workflow following a compromise event referenced by BED-7720.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch BED-7720-nuke_trivy

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can scan for known vulnerabilities in your dependencies using OSV Scanner.

OSV Scanner will automatically detect and report security vulnerabilities in your project's dependencies. No additional configuration is required.