slug: snyk-container
provider: Snyk Container
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 2
edges:
- tag: Issues
  spec_file: snyk-container-issues-api-openapi.yml
  capability_id: BC-620.40
  capability_id_l1: BC-620
  capability_name: Vulnerability Management
  confidence: 0.88
  evidence: 'GET /orgs/{org_id}/issues "List Container Issues"; GET /orgs/{org_id}/packages/issues "List
    Package Issues"; schema Issue — vendor: "find and fix vulnerabilities in container images"'
  reason: Issues here are vulnerability findings (CVEs) in container images and packages; retrieving and
    triaging them is vulnerability scanning/remediation, squarely Vulnerability Management. Not IT incident
    or service desk issues.
- tag: Container Projects
  spec_file: snyk-container-container-projects-api-openapi.yml
  capability_id: BC-620.40
  capability_id_l1: BC-620
  capability_name: Vulnerability Management
  confidence: 0.72
  evidence: '"List Container Projects" / "Get Project SBOM" within an API that "provides vulnerability
    scanning and remediation for container images, Kubernetes workloads, and Helm charts"'
  reason: Projects are the organising unit for container vulnerability scans; the surface (list/get/delete
    project, retrieve SBOM) serves the vulnerability scanning and remediation workflow, i.e. Vulnerability
    Management. Slight discount because the operations themselves are CRUD over scan scopes rather than
    findings.