Ext Ops Panel
Open dashboard
Comparison

repo-forensics vs Zovo Dependency Audit

repo-forensics is a plugin bundle for AI coding tools published by Alex Greenshpun. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Zovo Dependency Audit is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
Marketplacerepo-forensicsZovo Dependency Audit
Community marketplace alexgreensh/repo-forensics Listed
Version: 2.14.19
Forks (GitHub): 29
Stars (GitHub): 205
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

repo-forensics vs Zovo Dependency Audit
Factrepo-forensicsZovo Dependency Audit
Marketplaces that list it11
Stars (GitHub) (differs)205No figure on GitHub
Forks (GitHub) (differs)29No figure on GitHub
Last release (differs)2026-10-24Not published
Where it runs (differs)Installs as a plugin bundleRemote server (dependency-audit.zovo.one/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)4Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)PolyForm-Noncommercial-1.0.0Not stated
Repository (differs)github.com/alexgreensh/repo-forensicsNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-152026-11-08
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

repo-forensics

In its own words, on Community GitHub marketplaces:

Offline security scanner for AI-agent repos, skills, plugins, and MCP servers. 29 scanners detect prompt injection, MCP tool poisoning, credential exposure, malicious lifecycle hooks, package IOCs, CVEs, CISA KEV exposure, and post-incident traces. Zero dependencies. Zero telemetry.

Zovo Dependency Audit

In its own words, on Official MCP Registry:

Audit a dependency list for known vulnerabilities, licenses and outdated versions.

How to run each

repo-forensics As a Claude Code plugin

Claude Code
/plugin marketplace add alexgreensh/repo-forensics
/plugin install repo-forensics@alexgreensh-repo-forensics

Zovo Dependency Audit As a remote MCP server

Claude Code
claude mcp add --transport http dependency-audit https://dependency-audit.zovo.one/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: repo-forensics · What it can do: Zovo Dependency Audit · 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. 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