Skip to main content
Pro. For “should I run Penthera, Anthropic’s security review action, or both?”
Last checked: 2026-11-10 against the action’s README, prompts and action.yml at commit 0c6a49f.

Use them together

Claude Code Security Review is a GitHub Action (MIT) from Anthropic. Claude reads a pull request’s diff, reports the problems it is confident about, filters out likely noise in a second pass, and comments on the changed lines. It needs an API key, and the model decides what counts as a finding. Its own audit prompt leaves some ground to other tools on purpose. It tells the model to skip secrets stored on disk (“these are handled by other processes”), denial of service, and rate limiting, and its filter skips outdated third-party libraries. Penthera’s rules cover the first and the last, plus the parts no diff review sees: the lockfile, the agent config and the running app. A reasonable setup: the Claude review on pull requests from your own team, for logic and authorization bugs no rule describes. Penthera on every pull request, forks included, for what a rule can prove.

Side by side

Where the Claude review goes further

  • Bugs no rule names: broken authorization logic, a privilege check in the wrong place, data that leaks through an API response.
  • Any language, with the repository as context.
  • Line comments written for the person who opened the PR.

Where Penthera adds something

  • What its prompt leaves out: committed secrets and known-vulnerable or risky dependencies.
  • Outside the diff: install scripts, MCP servers and hooks, and the live app.
  • Fork PRs, which the Claude review should not see.
  • The same answer every run, and a rule id for every finding that you can read and argue with.

Run both

The Claude review only on PRs from branches in your own repository, Penthera on every PR. Pin both actions to a commit SHA, not a branch or tag.
Locally, before you push:
Then ask Claude Code for /security-review on the same change. All comparisons · Back to the README