Ext Ops Panel
Open dashboard
Comparison

42crunch-api-security-testing vs audit-project

42crunch-api-security-testing is a plugin bundle for AI coding tools published by 42Crunch-AI. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). audit-project is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplace42crunch-api-security-testingaudit-project
Claude Code: claude-plugins-official Listed
Version: 1.5.5
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 1.15.0
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 5.1.0
Forks (GitHub): 2
Stars (GitHub): 3
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

42crunch-api-security-testing vs audit-project
Fact42crunch-api-security-testingaudit-project
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)1 (worse)3 (better)
Forks (GitHub) (differs)1 (worse)2 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)54
Licence (differs)Apache 2.0MIT
Repository (differs)github.com/42crunch-ai/claude-pluginsgithub.com/agent-sh/audit-project
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

42crunch-api-security-testing

In its own words, on Claude Code: claude-plugins-official:

Automate API security directly in Claude Code with 42Crunch - automatically audit OpenAPI specs, detect vulnerabilities aligned with OWASP API Security risks (including BOLA/BFLA), and apply AI-powered fixes. Designed for AI-assisted development workflows, it provides continuous guardrails through an audit->scan->remediate->validate loop, ensuring APIs meet enterprise security standards before deployment.

audit-project

In its own words, on Claude Code: claude-plugins-community:

Multi-agent iterative code review until zero issues remain. Spawns up to 10 specialist reviewers (code quality, security, performance, test coverage, architecture, database, API, frontend, backend, DevOps) chosen based on the project's signals. Each pass produces certainty-graded findings (HIGH / MEDIUM / LOW); HIGH findings auto-fix where safe. The orchestrator iterates passes until zero open issues remain or a max-iteration cap is reached. Specialists are role-based (defined inline via Task tool, not file-based agents) so they don't bloat the plugin's agent count. Designed to plug into /next-task and /prepare-delivery as the deep-review phase.

How to run each

42crunch-api-security-testing As a Claude Code plugin

Claude Code
/plugin install 42crunch-api-security-testing@claude-plugins-official

audit-project

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: 42crunch-api-security-testing · What it can do: audit-project · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built