Next.js npm Package Metadata and Health

Use this endpoint when you need real-time npm registry data for Next.js or any other npm package — particularly useful for monitoring package health, checking latest versions, or enriching developer tooling workflows. Prefer this over manual npm CLI queries when operating in an automated agent pipeline that requires structured, up-to-date package metadata.

• Package name not found on npm registry — returns error or empty result
• npm registry temporarily unavailable — may return timeout or upstream error
• Invalid package name format — returns validation error
• Network or payment processing failure — endpoint may return 402 or connection error