Ext Ops Panel
Open dashboard
Comparison

dynos-audit vs sonarqube

dynos-audit is a plugin bundle for AI coding tools published by HassamSheikh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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). As of our marketplace pass on 2026-10-15. 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
Marketplacedynos-auditsonarqube
Claude Code: claude-plugins-community Listed
Version: 7.5.16
Forks (GitHub): 2
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 2.3.0
Forks (GitHub): 6
Stars (GitHub): 112
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 2.6.0
Forks (GitHub): 6
Stars (GitHub): 112
Not marked · First seen
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 2.6.0
Forks (GitHub): 6
Stars (GitHub): 112
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

dynos-audit vs sonarqube
Factdynos-auditsonarqube
Marketplaces that list it (differs)1 (worse)4 (better)
Stars (GitHub) (differs)2 (worse)112 (better)
Forks (GitHub) (differs)2 (worse)6 (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
Hooks it runs (differs)81
Parts of the bundle (differs)6312
Licence (differs)MITSSAL-1.0
Repository (differs)github.com/hassamsheikh/dynos-auditgithub.com/sonarsource/sonarqube-agent-plugins
Changes in the last 7 days (differs)02
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

dynos-audit

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

Description: Spec-driven audit enforcement for AI coding agents. Intercepts every phase transition with a mandatory audit loop. It builds a requirement ledger from your spec, audits the artifact, identifies gaps, delegates fixes, and re-audits until every requirement is provably done with evidence. Never accepts "mostly complete." Requires Superpowers.

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.

How to run each

dynos-audit As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dynos-audit@claude-community

sonarqube As a Claude Code plugin

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

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: dynos-audit · What it can do: sonarqube · 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 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 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