Snyk

“Snyk… checkmarx and veracode are becoming legacy applications because of Snyk. Hands-down. technology companies, heavy on the development side will have far greater success with Snyk than any of the others. And this is because the development team has a resistance to utilizing any of these sorts of technologies. What I mean by that is the security team will see the value and spend a lot and I mean a lot of money towards this value. However, the solution will never get fully integrated and utiliz”

“As a Snyk user, this is going to be a problem. Its almost expected now, company replaces their teams with AI , quality of their product drops. We have already walked away from some tooks for this same reason, its not taking an anti-AI stand, its because their product quality will suffer, and still charge us the same premium? Nah... just cancel”

“Honestly, Snyk as a product is shit. The APIs are inconsistent and difficult to work with, integrations lack feature parity for the same functionality. New features often take far too long to be fully rolled out. Capabilities such as identifying whether a dependency is only used during test are still missing. Reachability analysis, for example, was only introduced relatively recently, even though it has become a fundamental expectation in modern security tooling. They simply cannot compete with ”

“Snyk has been problematic at our company. I'm not sure how effective it is at shifting anywhere to be honest. Their website at first was ok. But then you start to use the product and realize what a dumpster fire the whole thing is. You'll naturally gravitate to using their API, hoping it's easier to get what you want. Nope. Talking about Snyk is also an exercise in mental gymnastics. A "project" is not what you think it is. I believe it's actually a reference to a file. Then you have their IDE p”

“Good product, easy setup, reason and flexible pricing — So far our company has adopted Snyk across our SDLC and incorporated it into our repos and pipelines and have enjoyed our experience with using Snyk so far. — Snyk simplifies security. It can scan your for vulnerabilities during development or when your run a pipeline in azure dev ops. This raises issues before they make it to production so you have the comfort of knowing that new and existing packages have no known security vulnerabilitie”

“As a Snyk user, this is going to be a problem. Its almost expected now, company replaces their teams with AI , quality of their product drops. We have already walked away from some tooks for this same reason, its not taking an anti-AI stand, its because their product quality will suffer, and still charge us the same premium? Nah... just cancel”

“Snyk stands out because it keeps application security simple and developer-friendly by integrating directly into the development workflow. It not only identifies vulnerabilities across code, dependencies, and containers, but also offers clear, automated fixes that help teams resolve issues faster and build secure software from the start. Snyk can sometimes produce false positives and generate too many alerts, which can overwhelm teams and force a lot of manual validation. It can also become expe”

“Snyk is easy to set up and start using. Setting it up to run as a GitHub Action allows it to integrate seamlessly alongside other existing CI processes. Along with this, I like that its vulnerability scanning is pretty much universally trusted amongst engineers, this trust allows for peace of mind. This might have changed since the last time I worked with this product, but at the time Snyk was a bit expensive compared to similar products. Snyk makes it easy to stay informed about possible vaulne”

“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 an”

“Snyk has been problematic at our company. I'm not sure how effective it is at shifting anywhere to be honest. Their website at first was ok. But then you start to use the product and realize what a dumpster fire the whole thing is. You'll naturally gravitate to using their API, hoping it's easier to get what you want. Nope. Talking about Snyk is also an exercise in mental gymnastics. A "project" is not what you think it is. I believe it's actually a reference to a file. Then you have their IDE p”

“Must have for UI development — Snyk is allowing us to make good use of the wealth of great open source software out there, without compromising on security. — It took only seconds to set up, yet works for my projects every day. Knowing what my venerabilities are during the development phase allows the evaluation of the concern prior to code ever seeing production — I wish it had a way to automatically inform the creators in the chain of dependencies so we as developers did not have to.”

“Honestly, Snyk as a product is shit. The APIs are inconsistent and difficult to work with, integrations lack feature parity for the same functionality. New features often take far too long to be fully rolled out. Capabilities such as identifying whether a dependency is only used during test are still missing. Reachability analysis, for example, was only introduced relatively recently, even though it has become a fundamental expectation in modern security tooling. They simply cannot compete with ”