slim-container-vulnerability-scanning

Automate vulnerability scanning for Docker images and package dependencies with Grype.

35|14|Updated Feb 16, 2022
One-click install
npx skills add https://github.com/NASA-AMMOS/slim --skill slim-container-vulnerability-scanning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slim-container-vulnerability-scanning
Source: https://github.com/NASA-AMMOS/slim/tree/main/static/marketplace/skills/slim-container-vulnerability-scanning
Command: npx skills add https://github.com/NASA-AMMOS/slim --skill slim-container-vulnerability-scanning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill automates the detection of security vulnerabilities in container images and project dependencies, reducing manual security checks and helping teams maintain a secure baseline.

Core Features & Use Cases

  • Automated Scans: Scan container images, base images, and package-manager dependencies (NPM, Maven, PyPI, etc.) for known CVEs.
  • Pre-commit & CI/CD Integration: Gate code commits and pipelines based on vulnerability findings to prevent vulnerable code from entering the repository.
  • Comprehensive Guidance: Provide remediation steps, suggested fixes, and actionable insights for identified vulnerabilities in a reproducible workflow.

Quick Start

Install Grype and ensure it is in your PATH. Run a manual scan of your repository dependencies with grype dir:. Set up automated pre-commit scanning by installing pre-commit, copying the pre-commit config to your repo root, and enabling the hook:

  • pip install pre-commit
  • cp assets/pre-commit-config.yml .pre-commit-config.yaml
  • pre-commit install
  • pre-commit run --all-files

Frequently Asked Questions about slim-container-vulnerability-scanning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate container vulnerability scanning in a CI/CD pipeline?

Automate container vulnerability scanning by integrating Grype into your CI/CD pipeline and pre-commit hooks to gate code commits based on detected CVEs in Docker images and package dependencies.

What is the best way to scan Docker base images for known CVEs?

Scan Docker base images for known CVEs using Grype to automatically identify security vulnerabilities in your container images and package-manager dependencies like NPM, Maven, and PyPI.

Do I need Grype and Docker to scan software dependencies for vulnerabilities?

Yes, you need Grype, Docker, Python, and Git installed in your environment to run automated vulnerability scans on container images and software dependencies.

Can I use pre-commit hooks to prevent vulnerable dependencies from being committed?

Yes, you can use pre-commit hooks to prevent vulnerable dependencies from being committed by installing pre-commit, adding the Grype configuration, and gating code commits based on vulnerability findings.

How do I manually scan my repository dependencies for security issues?

Manually scan your repository dependencies for security issues by installing Grype, ensuring it is in your PATH, and executing a directory scan command to detect known CVEs in your project files.

Does container vulnerability scanning provide remediation steps for identified issues?

Container vulnerability scanning provides remediation steps by outputting suggested fixes and actionable insights for identified vulnerabilities to help teams maintain a secure baseline.