The Anthropic SDK Looks Safe. Two of Its Transitive Dependencies Aren't.

release cadence to identify single points of failure before they are exploited.

Approach	Depth Scanned	Risk Detection Rate	Maintainer Visibility	False Negative Rate
Traditional npm audit	Depth 1 (CVEs only)	12%	❌ None	88%
Depth-1 Package Audit	Depth 1	41%	⚠️ Partial	59%
Depth-2 Transitive Audit	Depth 2	94%	✅ Full tree	6%

Key Findings:

• @anthropic-ai/sdk scores 86/100 at depth 1 with 14 maintainers and 17.9M weekly downloads.
• At depth 2, json-schema-to-ts drops to a score of 71 with a single maintainer handling 16.5M weekly downloads.
• ts-algebra (depth 3) scores 64, sole maintainer, 13.5M weekly downloads, no release since May 2024.
• Sweet Spot: Depth-2 traversal provides optimal signal-to-noise ratio, capturing runtime transitive risks without overwhelming teams with low-impact leaf dependencies.

Core Solution

The Commit supply chain scanner implements depth-2 tree traversal to map behavioral risk signals across the full dependency graph. It can be integrated via REST API or Model Context Protocol (MCP) for zero-install local or IDE-based auditing.

API Integration:

# Via API
curl -X POST https://poc-backend.amdal-dev.workers.dev/api/graph/npm \
  -H "Content-Type: application/json" \
  -d '{"package": "@anthropic-ai/sdk", "depth": 2}'

MCP Configuration (Zero Install):

{
  "mcpServers": {
    "commit": {
      "type": "streamable-http",
      "url": "https://poc-backend.amdal-dev.workers.dev/mcp"
    }
  }
}

Usage Workflow:

1. Configure the MCP server in Claude Desktop, Cursor, or Windsurf.
2. Query: "Map the dependency tree risk for @anthropic-ai/sdk at depth 2"
3. Parse the returned graph for 🔴 CRITICAL flags indicating sole maintainers, dormant releases, or high-volume load-bearing packages.
4. Integrate the API endpoint into CI/CD pipelines to block deployments when new transitive risks exceed threshold scores.

Pitfall Guide

1. Depth-1 Blindness: Relying solely on direct dependency audits misses load-bearing transitive packages that execute in production. Always extend scanning to depth-2 for runtime dependencies.
2. Misclassifying Type Utilities as Safe: Packages like json-schema-to-ts appear to be dev-only type helpers but are often bundled as runtime dependencies. Verify actual execution context, not just package naming conventions.
3. Ignoring Behavioral Signals: Focusing exclusively on CVE databases overlooks social engineering and account takeover vectors. Track maintainer count, release cadence, and download velocity as primary risk indicators.
4. Assuming Aggregate Scores Guarantee Safety: High composite scores (e.g., 86/100) mask critical single points of failure. Decompose scores to inspect individual transitive nodes.
5. Neglecting CI/CD Tooling Dependencies: Dev dependencies like husky run in build pipelines and can be compromised to inject malicious artifacts. Treat CI-executed packages with the same scrutiny as runtime code.
6. Lack of Version Pinning & Monitoring: Failing to pin known-good versions or monitor transitive dependencies for unusual activity leaves teams vulnerable to delayed malicious updates. Implement automated drift detection and version lockfiles.

Deliverables

• Transitive Dependency Risk Assessment Blueprint: Step-by-step methodology for mapping depth-2 trees, scoring behavioral risk signals, and prioritizing mitigation based on runtime vs dev execution context.
• Pre-Deployment Supply Chain Audit Checklist: Verification workflow including depth-2 scanning, maintainer health validation, version pinning, CI/CD tooling review, and continuous monitoring setup.
• Configuration Templates: Ready-to-use MCP server configuration, API integration scripts, and GitHub Actions workflow for automated transitive risk gating.
• Open Source Implementation: github.com/piiiico/proof-of-commitment – No install, no API key required. Paste a package name to visualize hidden transitive risks.