Governed ignores with Ignore Approval Workflow
Snyk Code findings can now be suppressed through an Ignore Approval Workflow that requires review, preventing developers from silently ignoring vulnerabilities without security team oversight.
Until now, a developer could suppress a Snyk Code finding on their own — directly in the Web UI or IDE — with no review step.
Suppression happened silently and unilaterally, leaving security teams without a gate on what got ignored.
Source: original entry ↗
More from Snyk
Follow Snyk to get its new changes in your feed and email digest.
Snyk CLI v1.1308.1 released
HTML report output is now available by default without preview features, and project names are consistently displayed in test summaries. This release also patches multiple security vulnerabilities.
Pending ignore requests now visible on Project's Issues page
Issues with pending ignore requests now display a clear "Pending Ignore Request" status on the Issues page and in issue details, with filtering support. The issues API now reports pending as part of an issue's ignore status for programmatic distinction of open, pending, and ignored findings.
Snyk Code October update: improved analysis and more findings
Snyk Code now analyzes projects more deeply and accurately across Java, Kotlin, Go, TypeScript, JavaScript, Python, C#, PHP and Ruby, with significantly more findings reported. Improvements include better import resolution via config files, corrected PHP typing, expanded library coverage, new vulnerability detection rules, and enhanced template and serverless application analysis.