Ext Ops Panel
Open dashboard
Comparison

latio-secure-supply-chain-skills vs io.github.flagrix-io/flagrix

latio-secure-supply-chain-skills is a plugin bundle for AI coding tools published by latiotech. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.flagrix-io/flagrix is an MCP server published by flagrix-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
Marketplacelatio-secure-supply-chain-skillsio.github.flagrix-io/flagrix
Claude Code: claude-plugins-community Listed
Version: 0.2.0
Forks (GitHub): 4
Stars (GitHub): 29
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Downloads/month (npm): 218
Downloads/week (npm): 48
Forks (GitHub): 0
Stars (GitHub): 2
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

latio-secure-supply-chain-skills vs io.github.flagrix-io/flagrix
Factlatio-secure-supply-chain-skillsio.github.flagrix-io/flagrix
Marketplaces that list it11
Stars (GitHub) (differs)29 (better)2 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (flagrix)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)19Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/latiotech/secure-supply-chain-skillsgithub.com/flagrix-io/flagrix-cli
Changes in the last 7 days00
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

latio-secure-supply-chain-skills

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

Audit and take action to secure your repository against supply chain misconfigurations and malware.

io.github.flagrix-io/flagrix

In its own words, on Official MCP Registry:

Scan GitHub repos and profiles for malware before cloning — commit-pinned risk verdicts for agents

How to run each

latio-secure-supply-chain-skills As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install latio-secure-supply-chain-skills@claude-community

io.github.flagrix-io/flagrix As a local MCP server: npm package

Claude Code
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio flagrix -- npx -y flagrix mcp

Requires: GITHUB_TOKEN (secret)

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

The marketplaces of latio-secure-supply-chain-skills publish no settings it asks for, so we do not compare settings.

What it can do: latio-secure-supply-chain-skills · What it can do: io.github.flagrix-io/flagrix · 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