A vulnerability scanner for container images, filesystems, and SBOMs to detect known security issues.
Grype is a vulnerability scanner that detects known security vulnerabilities in container images, filesystems, and Software Bill of Materials (SBOMs). It helps identify risks in software artifacts by matching packages against vulnerability databases, providing actionable security insights for developers and security teams.
Developers, DevOps engineers, and security professionals who need to scan container images, directories, or SBOMs for vulnerabilities as part of their CI/CD pipelines or security assessments.
Grype offers fast, accurate scanning with broad ecosystem support and threat prioritization features, making it a versatile tool for integrating vulnerability detection into modern development workflows without heavy overhead.
A vulnerability scanner for container images and filesystems
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports a wide range of OS packages (e.g., Alpine, Debian, RHEL) and language ecosystems (e.g., Ruby, Java, Python), enabling thorough vulnerability checks across diverse software stacks.
Integrates EPSS, KEV, and risk scoring to prioritize vulnerabilities based on exploit likelihood and impact, helping teams focus on high-risk issues quickly.
Can scan container images (Docker, OCI), filesystems, and SBOMs, making it adaptable for CI/CD pipelines and various artifact types without switching tools.
Supports the OpenVEX standard for filtering and augmenting scan results, enhancing vulnerability management with industry-standard exchange formats.
Operates solely via command-line, requiring additional tools or integrations for teams that prefer visual interfaces or dashboards, which can add complexity.
Relies on online access to update vulnerability databases; offline environments need manual updates or configurations, potentially hindering deployment in restricted networks.
Advanced features like custom risk scoring and OpenVEX usage require configuration files, increasing setup time and complexity for users seeking plug-and-play simplicity.