Scan your codebase for vulnerabilities changedclaude-security
Nearest release: v2.1.302, published 3 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 16 Oct 2026 20:27 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:37 UTC.
Upstream edited
Recorded here
Lines+18added
Lines−20removed
From line
55
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits18to this page, all time
The whole hunk
from line 55, old and new numbered
/
from line 55
5555
5656The plugin adds one command, `/claude-security`, which opens a menu of its three jobs: scanning the codebase, scanning a set of changes, and suggesting patches. The happy path runs a full scan, then turns its findings into patches:
5757
58<Steps>
59 <Step title="Open the Claude Security menu">
60 Run `/claude-security` and pick **Scan codebase**.
61 </Step>
58**1. Open the Claude Security menu**
6259
63 <Step title="Choose what to scan">
64 The plugin reads your repository first, then offers the whole repository or a focused area, with each option's file count and relative cost stated. Pick the whole repository, or answer "I don't know" and the plugin picks a sensible default for your repository's size.
65 </Step>
60Run `/claude-security` and pick **Scan codebase**.
6661
67 <Step title="Confirm the run">
68 A scan may take a while, may use a significant number of tokens, and needs Claude Code left open while it completes. Nothing runs until you confirm.
69 </Step>
62**2. Choose what to scan**
7063
71 <Step title="Read the report">
72 While the scan runs, it reports each stage as it starts, with the detail available under [`/workflows`](/docs/en/workflows). Results are written to a timestamped directory in your repository, described in [Read the scan results](#read-the-scan-results).
73 </Step>
64The plugin reads your repository first, then offers the whole repository or a focused area, with each option's file count and relative cost stated. Pick the whole repository, or answer "I don't know" and the plugin picks a sensible default for your repository's size.
7465
75 <Step title="Turn findings into patches">
76 Run `/claude-security` again and pick **Suggest patches**, then choose which findings to address. Reviewed patches are written to the report's `patches/` folder; [Fix findings](#fix-findings) covers how each patch is built and reviewed.
77 </Step>
66**3. Confirm the run**
7867
79 <Step title="Apply the patches you accept">
80 Apply each patch from your shell with `git apply`, in its own pull request. Patches are never applied automatically.
81 </Step>
82</Steps>
68A scan may take a while, may use a significant number of tokens, and needs Claude Code left open while it completes. Nothing runs until you confirm.
69
70**4. Read the report**
71
72While the scan runs, it reports each stage as it starts, with the detail available under [`/workflows`](/docs/en/workflows). Results are written to a timestamped directory in your repository, described in [Read the scan results](#read-the-scan-results).
73
74**5. Turn findings into patches**
75
76Run `/claude-security` again and pick **Suggest patches**, then choose which findings to address. Reviewed patches are written to the report's `patches/` folder; [Fix findings](#fix-findings) covers how each patch is built and reviewed.
77
78**6. Apply the patches you accept**
79
80Apply each patch from your shell with `git apply`, in its own pull request. Patches are never applied automatically.
8381
8482You don't have to start from the menu: ask for a job directly, as arguments to the command, such as `/claude-security scan my branch`, or in plain language, such as "scan commit abc1234". The plugin works best in [auto mode](/docs/en/permission-modes), which lets the scan's agents proceed without a permission prompt at each step.
8583
No line in this hunk matches that.