Grype
7.4#3 in software composition analysis softwareFree planFree planLinuxmacOSSelf-hostedWindows
Visit
| Fact | Grype | Mend SCA |
|---|---|---|
| Company legal name | Crunchbase identifies the maker as Anchore Inc., an active privately held company. | Crunchbase identifies the legal name as Mend Ltd. and lists WhiteSource as an alternative name. |
| Founded | 2016 | 2011 |
| Funding | Anchore announced a $20 million Series A led by SignalFire on January 22, 2020; VentureBeat reported that this brought total funding to about $30 million. | Startup Nation Central reports $121 million in cumulative funding across five rounds and 201–500 employees. |
| Headquarters | Santa Barbara, California, United States | Givatayim, Israel |
| Integrations | The installation documentation provides a Docker image and lists community installation options including Homebrew, MacPorts, Winget, Scoop, and Snapcraft. | The integrations page lists GitHub, GitLab, Bitbucket, Azure DevOps, Jira, ServiceNow, Jenkins, Docker, JFrog Artifactory and several IDEs. |
| Intended users | The project documentation describes individual package scanning as useful for lightweight vulnerability checks and compliance scanning of specific dependencies. | Mend positions SCA for developers and security and legal teams managing open source security and compliance risks. |
| Purpose | Grype scans container images, filesystems, and SBOMs for known vulnerabilities. | Mend SCA identifies, prioritizes and remediates security and license risks in applications’ open source components. |
| Risk prioritization | Results can be sorted by severity, EPSS, KEV and risk scoring. | It combines CVSS 4.0 severity ratings and EPSS exploitability data with reachability analysis to prioritize vulnerabilities. |
Grype suits developers and teams checking packages, images, filesystems, or SBOMs for known vulnerabilities. Its individual-package scanning is also intended for lightweight checks and compliance reviews of specific dependencies.
Mend SCA suits developers and security and legal teams managing open source security and compliance risks. It is relevant to teams that need dependency reachability analysis, license controls, and SBOM workflows.