@digicatalyst/dep-diff-mcp

MCPattestedlive
v0.3.2Kaustubh GhodkeMITUpdated 1mo agonpmGitHub

MCP server that translates a lockfile diff into a human-readable upgrade plan.

Endpoint healthlive
checked 8 days ago · 335ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
87Downloads/wk
1GitHub stars
1mo agoLast update
Package
AuthorKaustubh Ghodke
LicenseMIT
Version0.3.2
Sourcenpm+mcp-registry
npm@digicatalyst/dep-diff-mcp
GitHubDigiCatalyst-Systems/dep-diff-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 2e95f21
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · none privileged
Security scan✓ Cleanv0.2.1 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagev0.2.1 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

analyze_package_changeGiven one package and two versions (from -> to), returns a structured upgrade analysis:

Given one package and two versions (from -> to), returns a structured upgrade analysis:

No input schema was published for this tool.

analyze_packages_bulkAnalyzes a list of package upgrades in parallel and returns a unified risk report with

Analyzes a list of package upgrades in parallel and returns a unified risk report with

No input schema was published for this tool.

review_dependabot_prGenerates a user message instructing the model to analyze a list of dependency changes, then call analyze_packages_bulk to produce a ranked risk report.

Generates a user message instructing the model to analyze a list of dependency changes, then call analyze_packages_bulk to produce a ranked risk report.

No input schema was published for this tool.

ecosystemPackage ecosystem (npm or pypi)

Package ecosystem (npm or pypi)

No input schema was published for this tool.

changesRaw list of changes, one per line, formatted as 'name from_version -> to_version'.

Raw list of changes, one per line, formatted as 'name from_version -> to_version'.

No input schema was published for this tool.

explain_package_upgradeGenerates a user message asking the model to analyze a specific package version bump and explain the risk.

Generates a user message asking the model to analyze a specific package version bump and explain the risk.

No input schema was published for this tool.

namePackage name

Package name

No input schema was published for this tool.

fromVersionCurrent version

Current version

No input schema was published for this tool.

toVersionTarget version

Target version

No input schema was published for this tool.

dep-diff-mcpTranslates a lockfile diff into a human-readable upgrade plan for npm and PyPI.

Translates a lockfile diff into a human-readable upgrade plan for npm and PyPI.

No input schema was published for this tool.

10 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server that translates a lockfile diff into a human-readable upgrade plan.

Keywords
mcpmodel-context-protocoldependencieschangelogcvedependabotcursor
Alternatives
Comparing tool surfaces…

Tools exposed

10 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 5 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

57 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+45 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in security