Ext Ops Panel
Open dashboard
Comparison

security-sweep vs CodeVulnerability

security-sweep is a plugin bundle for AI coding tools published by Onome-AJ. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). CodeVulnerability is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplacesecurity-sweepCodeVulnerability
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 2
Stars (GitHub): 12
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

security-sweep vs CodeVulnerability
Factsecurity-sweepCodeVulnerability
Marketplaces that list it11
Stars (GitHub) (differs)12No figure on GitHub
Forks (GitHub) (differs)2No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (codevulnerability-mcp.vercel.app/api/mcp)
Transport (differs)Not statedSSE
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/onome-aj/security-sweep-pluginNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

security-sweep

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

Comprehensive security scanner for codebases. Scans for hardcoded secrets (30+ API key formats), injection flaws (SQLi, XSS, command injection, SSRF), authentication issues (JWT misuse, weak password hashing)misconfigurations (CORS, debug mode, insecure TLS, Docker/K8s), dependency risks, AI-specific vulnerabilities (prompt injection, API key exposure, excessive agent permissions), mobile security issues (Android/iOS), and data exposure (PII in logs, weak crypto). Covers OWASP Top 10 (2025), Mobile Top 10 (2024), and LLM Top 10 (2025). Supports Python, JavaScript/TypeScript, Java/Kotlin, Go, Ruby, PHP, C#, Swift, and Dart with framework-aware checks that reduce false positives.

CodeVulnerability

In its own words, on Official MCP Registry:

OWASP threat scanner auditing codebases for safety leaks.

How to run each

security-sweep

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

CodeVulnerability

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: security-sweep · What it can do: CodeVulnerability · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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