← All use cases

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.

Advanced
1h

Skills & Plugins

  • GitHub
    Inspects repository files, pull requests, workflows, and history, using the connector first and the local git and gh tools where it falls short.

Starter prompt

A security advisory just went out for a compromised release of an npm package, and I've pasted the advisory link below. Without installing or running anything, check our package.json files, lockfiles, CI workflows and install scripts for any use of the affected versions. Report each finding as confirmed, needs verification or ruled out, with its severity and the file evidence, and stop there until I approve a fix.

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