io.github.TweedBeetle/dependency-fitness-mcp

MCPcommunity
v0.1.1io.github.TweedBeetleUnknownUpdated 25d agonpmGitHub

npm dependency fitness: deprecated/yanked/superseded + verified safe migration target.

Is this npm package safe to depend on — and if not, what do I move to? An MCP server that gives a coding agent a cross-validated fitness verdict for an npm package before it writes or upgrades a dependency: It reconciles four free, sanctioned sources — the npm registry, Google's deps.dev, OSV.dev, and GitHub — into one confidence-scored answer, and infers a safe migration target when a package is…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
25d agoLast update
Package
Authorio.github.TweedBeetle
LicenseUnknown
Version0.1.1
Sourcemcp-registry
npmdependency-fitness-mcp
GitHubTweedBeetle/dependency-fitness-mcp
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ 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>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface2 tools · none privileged
Security scan✓ Cleanv0.1.1 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Is this npm package safe to depend on — and if not, what do I move to? An MCP server that gives a coding agent a cross-validated fitness verdict for an npm package before it writes or upgrades a dependency: It reconciles four free, sanctioned sources — the npm registry, Google's deps.dev, OSV.dev, and GitHub — into one confidence-scored answer, and infers a safe migration target when a package is deprecated or superseded. "Is it deprecated?" is already free — deps.dev serves that flag, and…

Keywords
mcp