Some of what you see here is sample content. While the community forms, part of the members, reviews, ratings and discussions are seeded examples. Every one is badged Sample, and they do count towards the totals on this site. Vendor pages, the security data and the tools are real.
Developers actually use it, which is the whole battle
4.0/5overall, average of the five axes
Deployment effort5
Support quality4
Features vs promises4
Pricing transparency3
Return on investment4
What happened
The reason we kept Snyk is that engineers run it themselves. IDE and pull request integration means findings arrive where the work happens rather than in a monthly PDF nobody reads. False positives in dependency scanning still need triage discipline, and the licence cost grows with your developer count in a way finance will notice.
Worked well
Developer adoption is real. IDE and PR integration. Good remediation advice with fix PRs.
Did not
False positives need triage. Cost scales with developer count. Container scanning is weaker than the SCA piece.
10 found this helpful