What ships with the skill
The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.
- files
- 8
- Markdown files
- 5
- scripts
- 2
- references
- 4
- Size
- 38.3 KB
- Structural complexity
- Low
File inventory
PathTypeBytes
skills/scanning-container-images-with-grype/assets/template.mdReference2.1 KB
skills/scanning-container-images-with-grype/LICENSEOther11 KB
skills/scanning-container-images-with-grype/references/api-reference.mdReference1.7 KB
skills/scanning-container-images-with-grype/references/standards.mdReference2.5 KB
skills/scanning-container-images-with-grype/references/workflows.mdReference4 KB
skills/scanning-container-images-with-grype/scripts/agent.pyScript4.9 KB
skills/scanning-container-images-with-grype/scripts/process.pyScript6.4 KB
skills/scanning-container-images-with-grype/SKILL.mdInstruction5.8 KB
SKILL.md frontmatter
{
"name": "scanning-container-images-with-grype",
"description": "Scans container images, filesystems, and SBOMs for known CVEs with Anchore Grype, matching Syft-generated SBOM packages against NVD, GitHub Advisories, and OS-specific feeds with configurable severity thresholds and failure gates. Use when Grype or Syft is the chosen toolchain, when scanning an existing SBOM rather than an image, or when gating a build on severity. Keywords: Grype, Syft, SBOM, NVD, GitHub Advisory, --fail-on, severity threshold. Do not use when the toolchain is Trivy - use scanning-docker-images-with-trivy.",
"domain": "cybersecurity",
"subdomain": "container-security",
"tags": [
"grype",
"vulnerability-scanning",
"container-security",
"sbom",
"anchore",
"supply-chain"
],
"version": "1.0",
"author": "mahipal",
"license": "Apache-2.0",
"nist_csf": [
"PR.PS-01",
"PR.IR-01",
"ID.AM-08",
"DE.CM-01"
],
"mitre_attack": [
"T1610",
"T1611",
"T1609",
"T1525",
"T1195"
]
}