Snyk secrets scanner reaches general availability
Snyk secrets scanner is now generally available to detect and prevent hardcoded credentials, API keys, and tokens across repositories, with machine learning-driven detection that works for both human-written and AI-generated code. This helps protect your entire software development lifecycle against credential leaks and breaches.
Starting August 4, 2026, Snyk secrets scanner is generally available to help secure your entire SDLC against credential leaks.
Stolen credentials remain a leading initial access vector in security breaches, and the rise of AI-generated code increases the risk of exposing sensitive data. You can now use Snyk secrets scanner to detect hardcoded credentials, API keys, and tokens across your repositories and prevent them from reaching commits or being leaked.
Key capabilities include:
Machine learning driven detection and prevention across your development surfaces.
Secrets detection for both human-written and AI-generated code.
Governance and finding management directly within the Snyk web UI.
For more information, please read the blog and Snyk Secrets documentation
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.