Privacy and security
What the CLI sends
The CLI downloads public feeds and queries public APIs. It sends nothing about your project beyond what it is given, and no telemetry.
| To | What |
|---|---|
| Every source | A plain request for the feed, with a stackalarm/<version> user agent. |
| NVD and EUVD | Each tag and keyword, as a search term, with the date range. |
| GitHub API | The package names passed with --package or the profile, to filter the GitHub Advisory Database; your GITHUB_TOKEN when set. |
| NVD API | Your NVD_API_KEY when set. |
Responses are cached for an hour on your machine, in your user cache folder.
What the skill does
It runs on your machine, inside your agent: it reads the project, runs your own audit tools locally, and its web searches go through your agent like any other. It changes a file only after you agree, one change at a time, and never pushes, deploys or touches a server.
The triage in CI
On GitHub, with an ANTHROPIC_API_KEY, Claude reads the news, which is text written by others and could hold instructions
aimed at it. So it runs locked down: it can read the project, search the web, run read-only commands and write two answer files, nothing
more. It cannot open issues, push or change the project's files; the action opens the issue from its decision. The
exact list of allowed tools is read from the action.
The workflow to copy grants contents: read and issues: write only, and checks the repository out without keeping
its credentials.
Report a vulnerability
Privately, through GitHub's private vulnerability reporting, not in a public issue. See SECURITY.md and security.txt.