chore: set SCA threshold to high

[PeterSchafer]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Where should the reviewer start?

How should this be manually tested?

What's the product update that needs to be communicated to CLI users?

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 No relevant tests

🔒 Security concerns Sensitive information exposure: While this PR doesn't expose a secret, it intentionally weakens the security gate of the CI pipeline. By ignoring Medium/Low vulnerabilities, the project becomes more susceptible to supply chain attacks where lower-severity issues are chained or eventually upgraded to high/critical.

⚡ Recommended focus areas for review Reduced Security Visibility 🟠 [major] Setting open-source-scan to high prevents the CI pipeline from failing on (and potentially reporting) Medium and Low severity vulnerabilities. For a security product like the Snyk CLI, maintaining visibility into all vulnerability tiers is standard practice to prevent the accumulation of technical debt and security risk. This change allows vulnerabilities that might otherwise be blocked to enter the main branch unnoticed. open-source-scan: high

📚 Repository Context Analyzed This review considered 5 relevant code sections from 4 files (average relevance: 0.76) CONTRIBUTING.md (2 segments, lines 218-387) dangerfile.js (lines 1-111) help/README.md (lines 1-19) release-scripts/validate-repository.sh (lines 1-63)