Ext Ops Panel
Open dashboard
Comparison

dep-env-awareness vs Dockerfile Audit

dep-env-awareness is a plugin bundle for AI coding tools published by Pierre-louis242. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Dockerfile Audit is an MCP server published by UnbearableDev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplacedep-env-awarenessDockerfile Audit
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry 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

dep-env-awareness vs Dockerfile Audit
Factdep-env-awarenessDockerfile Audit
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (unbearable-dev--dockerfile-audit.apify.actor/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/pierre-louis242/dep-env-awarenessgithub.com/unbearabledev/dockerfile-audit
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 days 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

dep-env-awareness

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

Audit project dependencies, environment configuration, and runtime compatibility across Node, Python, Rust, Go, PHP, Ruby, and Java. Diagnoses version conflicts, lock file drift, CI/local mismatches, Docker image drift, and security vulnerabilities. Includes a quick triage mode for broken builds and a full five-phase audit with structured remediation reports. Useful for any developer hitting "it works on my machine" issues or wanting a health check before a release.

Dockerfile Audit

In its own words, on Official MCP Registry:

Hadolint-grade Dockerfile audit — 19 checks: secrets, privileges, supply chain, hygiene.

How to run each

dep-env-awareness As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dep-env-awareness@claude-community

Dockerfile Audit As a remote MCP server

Claude Code
claude mcp add --transport http dockerfile-audit https://unbearable-dev--dockerfile-audit.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only Dockerfile Audit 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

Neither one's marketplaces publish the settings it asks for.

What it can do: dep-env-awareness · What it can do: Dockerfile Audit · 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