Ext Ops Panel
Open dashboard
Comparison

ronce vs com.gitkraken/gk-cli

ronce is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.

ronce is a plugin bundle for AI coding tools published by Cedric Chariere Fiedler. No marketplace we read lists it any more. com.gitkraken/gk-cli is an MCP server published by gitkraken.com. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceroncecom.gitkraken/gk-cli
Community marketplace charierefiedler/ronce-racine Removed on 2026-10-24
Version: 0.5.2
Forks (GitHub): 0
Stars (GitHub): 8
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.1.77
Downloads/month (npm): 106 261
Downloads/week (npm): 23 741
Forks (GitHub): 375
Stars (GitHub): 461
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Claude: knowledge-work-plugins Not listed Listed
Version: 1.0.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

ronce vs com.gitkraken/gk-cli
Factronceno longer listed · com.gitkraken/gk-cli
Marketplaces that list it (differs)03
Stars (GitHub) (differs)8461
Forks (GitHub) (differs)0375
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleOn your machine (@gitkraken/gk)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published1
LicenceNot statedNot stated
Repository (differs)github.com/charierefiedler/ronce-racinegithub.com/gitkraken/gk-cli
Changes in the last 7 days (differs)40
First seen (differs)2026-10-222026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of ronce

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • aport-guardrails

    Security guardrails for Claude Code. Intercepts every tool call via PreToolUse hook and evaluates it against your Open Agent Passport (OAP) policy before execution. Blocks…

    by aporthq · Plugin bundle

    Listed on: Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job

  • claude-governance

    Governance templates that make Claude Code follow your architecture, security rules, and team conventions automatically — across Java, Python, Go, .NET, PHP, and JavaScript stacks.

    by datallmhub · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • coding-agent-rollout

    Roll Claude Code out to a team with guardrails you can check. Four deterministic stdlib scripts: a settings linter that reads shared, local, user and managed settings together…

    by Alireza Rezvani · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • clawkeeper

    Frictionless security, compliance, and threat detection for Claude Code and Co-Work. Advanced Behavioral detection patterns catch credential exfiltration, reverse shells, prompt…

    by rad-security · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • axme-code

    Persistent memory, architectural decisions, and safety guardrails for Claude Code. Your agent starts every session with full project context.

    by AxmeAI · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • raven-guard

    Production protection layer for Claude Code. Hard-blocks destructive operations (force push, DROP TABLE, TRUNCATE, Terraform state edits). P1/P2/P3 incident SLAs with escalation…

    by giggsoinc · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

ronce

In its own words, on Community GitHub marketplaces:

Guardrails, output shaping and telemetry for Claude Code sessions, driven by a per-project policy.

com.gitkraken/gk-cli

In its own words, on Official MCP Registry:

The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.

How to run each

ronce

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

com.gitkraken/gk-cli As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio gk-cli -- npx -y @gitkraken/gk 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: ronce · What it can do: com.gitkraken/gk-cli · Compare two other plugins

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. 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/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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