NPM Package Dependency Tree Analyzer

Use this endpoint when you need a structured, categorized breakdown of an npm package's dependencies — especially for dependency auditing, bundle bloat analysis, or understanding peer/optional dependency requirements. Prefer this over manually parsing package.json when you need counts and version constraints in one call without setting up a local npm environment.

• Package not found on npm registry — returns error indicating unknown package
• Invalid or non-existent version specified — returns version-not-found error
• Missing required query parameters (package or version) — returns 400 bad request
• Payment not included or invalid — returns 402 Payment Required
• Network timeout fetching registry data — returns 503 or timeout error