Ext Ops Panel
Open dashboard
Comparison

sonarqube vs Husk

sonarqube is a plugin bundle for AI coding tools published by SonarSource. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Copilot CLI: github/awesome-copilot, Claude Code: claude-plugins-community, Community GitHub marketplaces). Husk is an MCP server published by husk-security. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
MarketplacesonarqubeHusk
Claude Code: claude-plugins-official Listed
Version: 2.6.0
Forks (GitHub): 6
Stars (GitHub): 112
Not marked · First seen
Not listed
Copilot CLI: github/awesome-copilot Listed
Version: 2.6.0
Forks (GitHub): 6
Stars (GitHub): 112
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 2.3.0
Forks (GitHub): 6
Stars (GitHub): 112
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (npm): 242
Downloads/week (npm): 34
Forks (GitHub): 2
Stars (GitHub): 6
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

sonarqube vs Husk
FactsonarqubeHusk
Marketplaces that list it (differs)4 (better)2 (worse)
Stars (GitHub) (differs)112 (better)6 (worse)
Forks (GitHub) (differs)6 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (husk-sec)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)122
Licence (differs)SSAL-1.0MIT
Repository (differs)github.com/sonarsource/sonarqube-agent-pluginsgithub.com/husk-security/husk
Changes in the last 7 days22
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

sonarqube

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

Automatically enforce SonarQube code quality and security in the agent coding loop — 7,000+ rules, secrets scanning, agentic analysis, and quality gates across 40+ languages. PostToolUse hooks run analysis after every file edit. Pre-tool secrets scanning prevents 450+ patterns from reaching the LLM. Slash commands give on-demand access to quality gate status, coverage, duplication, and dependency risks. Includes SonarQube CLI, MCP Server, skills, hooks, and slash commands.

Husk

In its own words, on Official MCP Registry:

Local-first defensive scanner for vulnerable dependencies, leaked secrets, and risky agent configs

How to run each

sonarqube As a Claude Code plugin

Claude Code
/plugin install sonarqube@claude-plugins-official

Husk As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio husk -- npx -y husk-sec mcp

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: sonarqube · What it can do: Husk · 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/github/awesome-copilot/blob/HEAD/.github/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. 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