The docs.
Start with Getting started. The references are generated from the CLI itself, so they say what --help says.
Start
01
Getting started
The shortest path from nothing to a first check, first without an account, then with a workspace that keeps findings.
Reference
04
The inventory format
What the CLI writes and sends: packages, runtimes, images and what could not be read.
05
The API for host applications
Show watchdep's findings inside another of your applications, record decisions on behalf of its people, and hear about every state change.
Concepts
07
Decisions and a finding's life
The states a finding moves through, the decisions a person can make, and the log that records every change.
08
Alerts
What tells people about a finding, how each person chooses when they hear, and the workspace webhook.
09
The code check
How watchdep check answers whether your code uses an affected package, where it runs, and what leaves your machine.
10
AI review
How watchdep reviews findings with Claude and Gemini, what a review can and cannot do, what is sent, and how to turn it off or bring your own key.
11
Fixes and pull requests
Choosing per level whether watchdep names the fix or opens a pull request, how the fixers work, and what production means.
12
Dependencies and SBOM
What every application depends on, side by side across its parts, a package's own page, and exporting a standard SBOM.
Connect
13
Connecting GitHub
Let your watchdep server take a part's inventory from GitHub itself, with read-only access, on every push and every night.
14
The Action and CI
Run watchdep in GitHub Actions with watchdep-action, or call the command line from any other CI system.
15
Agents (MCP)
Connect Claude Code or another MCP client to watchdep, so it can read findings and, if you allow it, record decisions as you.
Run
16
The hosted service
How the hosted service works: signing up, workspaces, and how each one is kept apart.