Audit dependency incidents
Turn an advisory about a public package into a safe plan to audit your repository.
Point ZeroTwo at an advisory about a public package or its supply chain and it runs a read-only audit, going through manifests, lock files, CI workflow files, and scripts while never executing untrusted code.
Related links
Skills & Plugins
- GitHubInspects repository files, pull requests, workflows, and history, using the connector first and the local
gitandghtools where it falls short.
Starter prompt
Start with a safe audit plan
First produce a conservative checklist of what changed and what would prove exposure, before installing or running anything.
Keep the first pass read-only
Supply the advisory, separate authoritative sources, define proof of exposure, and inspect manifests, lock files, CI and scripts without executing them.
Report evidence status separately from severity
Rate each finding as confirmed, needs verification or ruled out, alongside severity. Plan remediation afterwards, as its own step.
Related use cases
Run a deep security scan
Dig through an authorized repository for plausible vulnerabilities.
Run your first security scan
Look for weaknesses in your code, inspect the supporting evidence, and choose what to act on.
Scan code changes for security
Look over a pull request or a local diff and catch security regressions before they land.


