Ext Ops Panel
Open dashboard
Comparison

gh-guard vs codeitall

gh-guard is a plugin bundle for AI coding tools published by sbom-tool. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). codeitall is an MCP server published by codeitall.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacegh-guardcodeitall
Claude Code: claude-plugins-community Listed
Version: 0.2.1
Forks (GitHub): 2
Stars (GitHub): 15
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
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

gh-guard vs codeitall
Factgh-guardcodeitall
Marketplaces that list it11
Stars (GitHub) (differs)15 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.codeitall.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)19Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/sbom-tool/gh-guardgithub.com/codeitalldev/codeitall
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

gh-guard

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

GH-Guard hardens CI/CD pipelines for Rust projects. It generates production-tested GitHub Actions workflows with SHA-pinned actions, OIDC-based Trusted Publishing, SLSA L3 provenance, and layered dependency auditing via cargo-deny, Dependabot, and osv-scanner. Five commands: /audit scans your repo against supply chain best practices, /harden walks you through fixes at three levels (Minimal/Standard/Hardened), /generate creates individual config files, /check-updates catches stale SHA pins, and /verify validates everything before you push. 14 skills provide deep context on Scorecard checks, dangerous workflow patterns, release automation, workspace publishing, fuzz testing, and compromised action incident response. All guidance is informed by real-world incidents including the March 2026 Trivy tag hijacking.

codeitall

In its own words, on Official MCP Registry:

Behavioral oracle for Rust crate APIs: runtime behavior, yank/advisory, deprecation, sig search

How to run each

gh-guard As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install gh-guard@claude-community

codeitall As a remote MCP server

Claude Code
claude mcp add --transport http codeitall https://api.codeitall.dev/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: gh-guard · What it can do: codeitall · 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