Need advice about which tool to choose?Ask the StackShare community!
Gemnasium vs WhiteSource: What are the differences?
Developers describe Gemnasium as "Parses your project's dependencies and notifies you when new versions are released or they need to be updated". Gemnasium keeps track of projects dependencies. Ruby, Node.js, PHP composer, Bower and Python projects dependencies are automatically parsed, and notifications sent when new versions are released or security advisories are published. On the other hand, WhiteSource is detailed as "*Continuously monitoring open source libraries for vulnerabilities *". It automatically identifies all the open source components and dependencies in your build by constant and automatic cross-referencing of your open source components.
Gemnasium and WhiteSource belong to "Dependency Monitoring" category of the tech stack.
Some of the features offered by Gemnasium are:
- Know about security vulnerabilities affecting your code
- Know when new versions of your dependencies gets released
- Know what changed with integrated changelogs
On the other hand, WhiteSource provides the following key features:
- Open Source Code Identification
- Vulnerable Components Mapping
- License & Identity Risks Discovery
I'm beginning to research the right way to better integrate how we achieve SCA / shift-left / SecureDevOps / secure software supply chain. If you use or have evaluated WhiteSource, Snyk, Sonatype Nexus, SonarQube or similar, I would very much appreciate your perspective on strengths and weaknesses and how you selected your ultimate solution. I want to integrate with GitLab CI.
I'd recommend Snyk since it provides an IDE extension for Developers, SAST, auto PR security fixes, container, IaC and includes open source scanning as well. I like their scoring method as well for better prioritization. I was able to remove most of the containers and cli tools I had in my pipelines since Snyk covers secrets, vulns, security and some code cleaning. SAST has false positives but the scoring helps. Also had to spend time putting some training docs but their engineers helped out with content.