x-scan-container-security
Scans Docker images for CVEs and Dockerfile best practices violations. Uses Trivy, Grype, or Snyk Container. Produces SARIF output with scoring.
- License 许可
- MIT
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- x-scan-container-security
- description
- Scans Docker images for CVEs and Dockerfile best practices violations. Uses Trivy, Grype, or Snyk Container. Produces SARIF output with scoring.
- allowed-tools
- Read, Write, Bash, Grep, Glob
- argument-hint
- [--image name:tag] [--dockerfile path] [--severity-threshold CRITICAL|HIGH|MEDIUM|LOW] [--ignore-unfixed]
- user-invocable
- true
- requires-capabilities
- []
02 资源文件 1
- 参考文档README.md1.7 KB
03 SKILL.md 正文
Global Output Policy
- Language: English ONLY.
- Tone: Technical, Direct, and Concise.
- Efficiency: Remove all conversational fillers and greetings to save tokens.
Skill: Container Security Scanner
Purpose
Scan Docker container images for known CVEs and analyze Dockerfiles for security best practices violations. Generate a combined SARIF 2.1.0 report with severity scoring and grade assignment.
Activation Condition
Include this skill when container security scanning is required for the project.
Triggers
/x-scan-container-security --image myapp:1.0-- scan image for vulnerabilities/x-scan-container-security --dockerfile ./Dockerfile-- lint Dockerfile for best practices/x-scan-container-security --image myapp:1.0 --dockerfile ./Dockerfile-- combined scan/x-scan-container-security --image myapp:1.0 --ignore-unfixed-- exclude CVEs without available fix
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
--image |
String | One of image/dockerfile required | (none) | Docker image name:tag to scan |
--dockerfile |
String | One of image/dockerfile required | ./Dockerfile | Path to Dockerfile to analyze |
--severity-threshold |
Enum | No | LOW | Minimum severity: CRITICAL, HIGH, MEDIUM, LOW |
--ignore-unfixed |
Boolean | No | false | Exclude CVEs without an available fix |
Workflow
Step 1 — Validate Parameters
- At least one of
--imageor--dockerfileMUST be provided - If
--imageis provided, validate name:tag format - If
--dockerfileis provided, validate file exists at path
Step 2 — Detect Scanning Tools
Check tool availability in order of preference:
| Priority | Tool | Image Scan | Dockerfile Lint | Detection Command |
|---|---|---|---|---|
| 1 | Trivy | Yes | Yes (config mode) | trivy --version |
| 2 | Grype | Yes | No | grype version |
| 3 | Snyk Container | Yes | No | snyk --version |
| 4 | hadolint | No | Yes | hadolint --version |
If no tools are available, produce a single INFO finding with installation instructions.
Step 3 — Image Vulnerability Scanning
Scan the Docker image for known CVEs in OS packages and application dependencies.
Trivy (Preferred)
trivy image --format json --severity CRITICAL,HIGH,MEDIUM,LOW {image}
Grype (Fallback)
grype {image} -o json
Snyk Container (Alternative)
snyk container test {image} --json
Step 4 — Dockerfile Linting
Analyze Dockerfile against 7 mandatory security checks:
| Check ID | Check Name | Severity | Fix Recommendation |
|---|---|---|---|
| DOCKER-001 | root-user | HIGH | Add USER <non-root-user> directive |
| DOCKER-002 | secrets-in-layers | CRITICAL | Use multi-stage build + .dockerignore |
| DOCKER-003 | latest-tag | MEDIUM | Specify exact image tag |
| DOCKER-004 | no-multi-stage | LOW | Use multi-stage build pattern |
| DOCKER-005 | unnecessary-packages | LOW | Add --no-install-recommends flag |
| DOCKER-006 | excessive-permissions | MEDIUM | Use restrictive permissions (755/644) |
| DOCKER-007 | missing-healthcheck | MEDIUM | Add HEALTHCHECK instruction |
Step 5 — Combine and Filter Findings
- Merge all findings from image scan and Dockerfile lint into a single collection
- Severity threshold: Exclude findings below the threshold
- Ignore unfixed: When
--ignore-unfixedis true, exclude CVE findings wherefixedVersionis empty
Step 6 — Generate SARIF Output
Produce SARIF 2.1.0 JSON combining all findings. Write to results/security/container-scan-YYYY-MM-DD.sarif.json.
Step 7 — Calculate Score and Grade
Start at 100, deduct per finding:
| Severity | Deduction |
|---|---|
| CRITICAL | -25 |
| HIGH | -15 |
| MEDIUM | -5 |
| LOW | -2 |
| Score Range | Grade |
|---|---|
| 90-100 | A |
| 80-89 | B |
| 70-79 | C |
| 60-69 | D |
| 0-59 | F |
Step 8 — Generate Markdown Report
Write report to results/security/container-scan-YYYY-MM-DD.md.
Error Handling
| Scenario | Action |
|---|---|
| No scanning tools installed | Return INFO finding with installation instructions, score 100 |
| Image not found locally | Suggest docker pull {image} first |
| Dockerfile not found | Report error with provided path |
| Scanner command fails | Report error, continue with other scanners |
| Neither --image nor --dockerfile provided | Error: at least one parameter required |
| Network error during scan | Suggest offline mode or retry |
CI Integration
GitHub Actions
- name: Container Security Scan
run: |
trivy image --format sarif --output trivy-results.sarif $IMAGE
- name: Upload SARIF
uses: github/codeql-action/upload-sarif@v3
with:
sarif_file: trivy-results.sarif
GitLab CI
container_scan:
stage: security
script:
- trivy image --format json --output gl-container-scanning-report.json $IMAGE
artifacts:
reports:
container_scanning: gl-container-scanning-report.json
Fail Conditions
| Condition | Action |
|---|---|
| Any CRITICAL CVE found | Fail pipeline (exit 1) |
| Dockerfile score < 70 | Fail pipeline (exit 1) |
| HIGH CVE count > threshold | Configurable warning/fail |
04 同仓库更多 Skills
x-parallel-eval
Detects and classifies file-collision risks between work units (tasks, stories, or epic phases) before parallel execution. Reads ## File Footprint blocks produced by x-task-plan / x-story-plan, applies the parallelism-heuristics knowledge pack (hard / regen / soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.
parallelism-heuristics
Canonical catalog of file-collision heuristics for parallel task, story, and epic execution. Defines the File Footprint block format, the three Conflict Categories (hard / regen / soft), a hotspot list of high-contention paths, and the degrade-with-warning policy. Consumed by x-task-plan, x-story-plan, x-epic-map, x-parallel-eval, and x-dev-*-implement.
x-watch-pr-ci
Polls a PR's CI checks and Copilot review status, blocking until checks complete or timeout. Returns one of 8 stable exit codes (SUCCESS=0, CI_PENDING_PROCEED=10, CI_FAILED=20, TIMEOUT=30, PR_ALREADY_MERGED=40, NO_CI_CONFIGURED=50, PR_CLOSED=60, PR_NOT_FOUND=70). Writes a versioned state-file for session resume.
x-validate-docs
Documentation freshness gate: validates 6 dimensions (readme, api-specs, grpc-proto, adr, skill-docs, system-architecture) against code changes in a PR. Stack-aware — only validates targets declared/auto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.
x-update-system-architecture
Incrementally updates docs/architecture/system.md after an epic completes. Appends new entries to the Decision Log (§11) using x-internal-write-report --append (dedup by ## ID: marker) and surgically inserts component/integration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.
x-update-architecture
Incrementally updates the service architecture document with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content. Use after implementation to keep architecture documentation current.