Snyk
Snyk helps teams find and fix vulnerabilities in code, dependencies, containers, and infrastructure. This integration reads organization, project, and issue metadata from Snyk — not local CLI scans.
Operational order
- Organizations — enumerate when org id or slug is unknown; save both on the credential.
- Projects — list or search monitored targets within the org before drilling into issues.
- Issues — list open findings for a project or repository prefix, then open one issue for remediation detail.
Entity hierarchy
- Organization — tenant boundary; every downstream read is org-scoped.
- Project — one monitored target (repo manifest, container image, IaC root, etc.).
- Issue — a finding on a project. Detail lookup uses the issue UUID from list results, not the human-readable SNYK key in dashboard URLs.
Workflows
- Onboarding — list organizations, pick the active org, store org id + slug on the credential, then list projects.
- Repository triage — search projects by repository path fragment, or list issues with a repository_name filter when one repo maps to several projects.
- Vulnerability review — list open issues with severity filters, then fetch one issue for upgrade and remediation metadata.
Gotchas
- Org scoping — wrong org id yields empty lists or not-found errors; confirm org membership first.
- Issue identity — single-issue reads require the UUID from list output; dashboard hash keys are not interchangeable.
- Repository filters — substring match on project names; typos or shortened paths may miss sibling projects.
- Read-only — no CLI scans, ignores, or policy edits through this bundle.
- Pagination — large orgs may return partial issue pages; follow pagination cursors when has_more is true.
