Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Secure Your AI Workflows: New Governance & Visibility Features from Snyk

As AI transforms software development, AppSec teams face new complexities. For instance, the lack of visibility into where AI is being used and the reality that AI-generated code is often highly vulnerable make it nearly impossible to prioritize remediation and effectively scale security programs. To succeed, AppSec teams have to evolve from task managers to strategic governance enforcers.

Speaking Different Languages: How to Align Dev and Sec Teams Effectively

Security issues in software development often stem not from developers’ lack of concern but from a fundamental disconnect between development and security teams. Each wants to do their job well, but their goals and expectations frequently conflict. This misalignment costs organizations in heightened security risks and tangible operational setbacks. Security issues identified too late in the cycle delay releases and increase project costs.

You Won't Believe These Results from Replit

In this video, we put Replit’s AI coding tool to the test by asking it to create a secure note-taking app. While the tool shows off some seriously impressive abilities, it’s not without its flaws... Join me as I explore what Replit can (and can’t) do, and whether AI coding tools such as this one are ready to build reliable, secure apps.

Snyk Named a Leader in the 2025 Forrester SAST Wave: SAST Solutions, Q3 2025

We’re excited to announce that Snyk has been recognized as a Leader in the Forrester Wave: Static Application Security Testing (SAST) Solutions, Q3 2025. This recognition affirms our place at the forefront of developer-first security — and highlights the innovation, customer impact, and platform breadth that continue to set us apart.

npm Supply Chain Attack via Open Source maintainer compromise

On Monday, September 8th, a highly regarded open source developer, ~qix, was compromised via a phishing email. ~qix is an author and maintainer behind a large number of popular npm packages and found himself caught by this attack after responding to a message from the email address of support help. This resulted in the attacker taking over his npm account and having access to publish malicious versions of packages to which Qix had privileged access.