npx claudepluginhub nasa-ammos/slim --plugin slim-rebrandingThis skill uses the workspace's default tool permissions.
This skill helps you implement comprehensive vulnerability scanning for containers and software dependencies using Grype, an open-source vulnerability scanner. It provides both manual scanning capabilities and automated integration through pre-commit hooks to detect security vulnerabilities early in the development process.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Monitors deployed URLs for regressions in HTTP status, console errors, performance metrics, content, network, and APIs after deploys, merges, or upgrades.
Provides React and Next.js patterns for component composition, compound components, state management, data fetching, performance optimization, forms, routing, and accessible UIs.
This skill helps you implement comprehensive vulnerability scanning for containers and software dependencies using Grype, an open-source vulnerability scanner. It provides both manual scanning capabilities and automated integration through pre-commit hooks to detect security vulnerabilities early in the development process.
The skill supports scanning containerized applications, base images, and package manager dependencies (NPM, Maven, PyPI, etc.) to identify known security vulnerabilities before they reach production.
Software:
Skills:
First, ensure Grype is installed and operational:
Install Grype:
# macOS (via Homebrew)
brew install anchore/grype/grype
# Linux/WSL
curl -sSfL https://raw.githubusercontent.com/anchore/grype/main/install.sh | sh -s -- -b /usr/local/bin
# Via Go
go install github.com/anchore/grype@latest
Verify installation:
grype version
Start with manual scanning to understand your current security posture:
Scan repository dependencies:
grype dir:.
This scans all package manager dependencies (package.json, requirements.txt, pom.xml, etc.) in the current directory.
Scan a specific container image:
# First build your container
docker build -t my-app:latest .
# Then scan the built image
grype my-app:latest
Scan a remote container image:
grype alpine:latest
grype nginx:1.21
Scan with severity filtering:
# Only show critical and high severity issues
grype dir:. --fail-on critical --fail-on high
Review scan output to understand vulnerabilities:
Address identified vulnerabilities:
For automated vulnerability checking before commits, set up pre-commit hooks:
Install pre-commit framework:
pip install pre-commit
Configure pre-commit scanning: Copy the pre-commit configuration to your repository root:
cp assets/pre-commit-config.yml .pre-commit-config.yaml
Initialize pre-commit in your repository:
pre-commit install
Test the setup:
pre-commit run --all-files
The automated scan will:
git push operationgrype dir:.git push --no-verify if neededFor automated scanning in your CI/CD pipeline:
GitHub Actions Integration:
General CI/CD Integration:
File: assets/pre-commit-config.yml
This template provides a ready-to-use pre-commit hook configuration that:
The configuration uses local repository execution to ensure reliable scanning without external dependencies.
grype db updateQ: The pre-commit scan is failing with "grype command not found"
A: Ensure Grype is installed and available in your PATH. Run grype version to verify installation. You may need to restart your terminal or update your PATH after installation.
Q: Scans are taking too long to complete A:
grype db updategrype dir:. --fail-on criticalQ: How do I skip the pre-commit scan temporarily?
A: Use git push --no-verify to bypass pre-commit hooks. However, this should be used sparingly and with caution.
Q: The scan found vulnerabilities but no fixes are available A:
Q: False positives are blocking development A:
Q: How often should I run vulnerability scans? A: