auto-approve-compound-bash vs io.github.jnMetaCode/shellward
auto-approve-compound-bash is a plugin bundle for AI coding tools published by oryband. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.jnMetaCode/shellward is an MCP server published by jnMetaCode. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  auto-approve-compound-bash |  io.github.jnMetaCode/shellward |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 6 Stars (GitHub): 20 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.5.11 Downloads/month (npm): 1 533 Downloads/week (npm): 279 Forks (GitHub): 24 Stars (GitHub): 140 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
| Fact | auto-approve-compound-bash | io.github.jnMetaCode/shellward |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 20 (worse) | 140 (better) |
| Forks (GitHub) (differs) | 6 (worse) | 24 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (shellward) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 0 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/oryband/claude-code-auto-approve | github.com/jnmetacode/shellward |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
auto-approve-compound-bash
Auto-approve compound Bash commands (pipes, chains, subshells) by parsing each segment via shfmt AST and checking against allow/deny lists
io.github.jnMetaCode/shellward
AI agent security: 7 MCP tools for injection detection, PII scanning, command safety, DLP.
How to run each
auto-approve-compound-bash As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install auto-approve-compound-bash@claude-communityio.github.jnMetaCode/shellward As a local MCP server: npm package
claude mcp add --transport stdio shellward -- npx -y shellwardCommands 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
The marketplaces of auto-approve-compound-bash publish no settings it asks for, so we do not compare settings.
What it can do: auto-approve-compound-bash · What it can do: io.github.jnMetaCode/shellward · 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.