G2

Prateek J.

DevSecOps Architect

Mid-Market (51-1000 emp.)

4/23/2026

"Seamless Dev-First Security with Fast Scans and Actionable Fixes"

4.5/5

What do you like best about Snyk?

What I like best about Snyk is how it integrates security into the developer workflow without disrupting it. The VS Code and JetBrains plugins give real-time vulnerability feedback as I write code, cutting remediation time significantly. Instead of just flagging a CVE, Snyk tells you exactly which version to upgrade to and often opens a fix PR automatically, saving hours of manual cross-referencing. The dependency graph makes transitive vulnerabilities easy to understand, and the reachability analysis means we focus on what's genuinely exploitable rather than drowning in false positives.

Performance-wise, scans run fast even on large monorepos, and the dashboard stays responsive without lag, it never feels like a bottleneck in the CI pipeline.

On pricing and ROI, the value becomes clear quickly. Catching vulnerabilities pre-deployment rather than post-production saves significant incident response costs, and the free tier is generous enough for smaller teams to see real value before committing. Onboarding was smooth too, connecting GitHub repos took minutes and gave us an immediate risk picture. It feels like a security tool built for developers, which makes adoption across engineering teams much easier. Review collected by and hosted on G2.com.

What do you dislike about Snyk?

A few friction points stand out. The noise from low-severity vulnerabilities can be overwhelming, especially on larger projects, while prioritization helps, tuning the filters to fit your specific risk tolerance takes time and trial and error. The licensing issue detection, though useful, sometimes flags things that aren't actually a concern in your use case, adding to that noise.

Pricing can become a pain point as teams scale. The jump between tiers feels steep, and some features that feel essential, like deeper reporting or SSO, are locked behind higher plans, which can be frustrating for mid-sized teams trying to justify the upgrade.

Occasionally the fix suggestions aren't actionable because the recommended version introduces breaking changes, so you still end up doing manual research. It would be more helpful if Snyk flagged compatibility risks alongside the fix recommendation. The Snyk Code (SAST) results can also feel less mature compared to the SCA side, more false positives and less context around why something is flagged.

Overall these are manageable drawbacks, but they do add friction for teams trying to run lean. Review collected by and hosted on G2.com.

What problems is Snyk solving and how is that benefiting you?

Snyk solves the core problem of security being an afterthought in the development lifecycle. Before using it, vulnerabilities were typically caught late, during dedicated security audits or worse, post-deployment, making fixes costly and disruptive. Snyk shifts that detection to where the code is actually written, which changes the economics of security entirely.

The biggest benefit has been reducing the gap between vulnerability discovery and remediation. Developers get context-rich alerts in their IDE and PRs rather than a spreadsheet from a security team weeks later, which means fixes happen faster and with less back-and-forth.

It also solves the visibility problem across open source dependencies. With complex dependency trees, it was previously difficult to know what you were actually running in production and whether it was safe. Snyk gives a clear, continuously updated picture of that risk without requiring manual audits.

From a team dynamic standpoint, it bridges the gap between developers and security teams by speaking the developer's language, showing fixes, not just findings. This has made security a shared responsibility rather than a blocker, which speeds up release cycles without compromising on risk management.

The ROI shows up in avoided incidents, faster PR cycles, and less time spent in reactive fire-fighting mode, all of which compound over time. Review collected by and hosted on G2.com.