Ext Ops Panel
Open dashboard
Comparison

dependency-evaluator vs Attestari

dependency-evaluator is a plugin bundle for AI coding tools published by apart-tech. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Attestari is an MCP server published by attestari.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplacedependency-evaluatorAttestari
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.9.0
Downloads/month (PyPI): 0
Downloads/week (PyPI): 343
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

dependency-evaluator vs Attestari
Factdependency-evaluatorAttestari
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.attestari.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/apart-tech/pluginsNot stated
Changes in the last 7 days (differs)41
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 35 h ago, requires a key

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

dependency-evaluator

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

Evaluate npm and Python packages before adding them as dependencies. Automatically gathers package metadata, analyzes source complexity, checks security and maintenance health, and produces a structured USE / EXTRACT / BUILD verdict. Auto-triggers when your agent is about to install a new package, or run on-demand with /evaluating-dependencies <package> [function]. Catches supply chain red flags like .pth injection, typosquatting, and stale maintainership.

Attestari

In its own words, on Official MCP Registry:

Attestari's verdict on an npm or PyPI package version, asked before an agent installs it.

How to run each

dependency-evaluator As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dependency-evaluator@claude-community

Attestari As a remote MCP server

Claude Code
claude mcp add --transport http attestari https://mcp.attestari.ai/mcp

Requires: ATTESTARI_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Attestari has a remote endpoint we check. How we check endpoints

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 dependency-evaluator publish no settings it asks for, so we do not compare settings.

What it can do: dependency-evaluator · What it can do: Attestari · 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 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