Is Dependency Fitness safe and trustworthy?

tashan scores Dependency Fitness on public evidence — tashan score 41.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Dependency Fitness?

In Claude Code: run `claude mcp add dependency-fitness -- npx -y dependency-fitness-mcp`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Dependency Fitness?

source: TweedBeetle/dependency-fitness-mcp.

‹ The Index

Dependency Fitness

npm

MCP server that returns a cross-validated dependency FITNESS verdict for npm packages: deprecated / yanked / superseded status plus an inferred safe migration target — what to move to and how confident we are — cross-checked across the npm registry, deps.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Security — see all ranked ›

Work: Application development · Logistics and fulfilment

Who it is for: Software engineer · Operations

Install (Claude Code):

claude mcp add dependency-fitness -- npx -y dependency-fitness-mcp

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Dependency Fitness scores 41 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down — and tells you the day it moves.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-dependency-fitness-mcp.svg)](https://tashan.sh/capability/pkg-dependency-fitness-mcp.html)

tashan score: 41.0
Adoption: 65/wk
Upkeep: 49.0
Freshness: 79.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 0.1.1

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

npm ↗ · source ↗ · pkg:dependency-fitness-mcp

Everything on this page is public evidence and free. What it cannot know is whether you run this — npx tashan-cli doctor reads your own config and names what is wrong in it, also free. tashan Pro tells you the day any of it changes.

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-10 · scorer s5 · how · something wrong here?