Search the npm registry for packages matching a query.

Returns a list of packages with name, version, description, keywords, and quality scores.

Args:

• query (string): Search query for npm packages

• limit (number): Maximum results to return, 1-30 (default: 10)

Returns: List of matching packages with metadata and scores. Each result includes:

• name, version, description, keywords

• links (npm, homepage, repository)

• scores (quality, popularity, maintenance, overall)

Examples:

• "react state management" -> finds Redux, MobX, Zustand, etc.

• "typescript orm" -> finds Prisma, TypeORM, Drizzle, etc.

• "zod" -> finds zod and related packages

Get comprehensive information about an npm package including latest version, description, license, homepage, repository, keywords, engines, and maintainers.

Args:

• package_name (string): The npm package name

Returns: Package metadata including:

• name, latest version, description

• license, homepage, repository URL

• keywords, engines (node/npm version requirements)

• dist-tags (latest, next, beta, etc.)

• maintainers list

• author information

Examples:

• "react" -> React package info with latest version, license, etc.

• "@anthropic-ai/sdk" -> Anthropic SDK details

List published versions of an npm package with release dates, sorted by most recent first.

Args:

• package_name (string): The npm package name

• limit (number): Maximum versions to return, 1-100 (default: 20)

Returns: Version list with publish dates, dist-tags, and deprecation notices. Includes:

• version number and publish date for each version

• dist-tags annotation (latest, next, beta, etc.)

• deprecation warnings where applicable

• total version count

Examples:

• "react" -> Lists recent React versions with dates

• "typescript", limit=5 -> Last 5 TypeScript releases

Get dependency information for a specific version of an npm package.

By default returns direct dependencies of all kinds (dependencies, devDependencies, peerDependencies, optionalDependencies) along with totals. When depth is greater than 1, resolves the transitive production dependency tree (using the abbreviated packument format and a bounded fetch limiter) and renders it as an ASCII tree with deduplicated nodes.

Args:

• package_name (string): The npm package name

• version (string, optional): Specific version to check (defaults to latest)

• depth (number, optional, 1-5): Transitive production-dep depth (default 1)

• include_dev (boolean, optional): Include devDependencies (default true; ignored when depth > 1)

• include_peer (boolean, optional): Include peerDependencies (default true; ignored when depth > 1)

• include_optional (boolean, optional): Include optionalDependencies (default true; ignored when depth > 1)

Returns:

• Counts summary (runtime/dev/peer/optional)

• Direct dependency lists by category

• When depth > 1: a transitive production-dep tree, deduplicated on resolved version

Examples:

• "express" -> Express direct dependencies at latest

• "react", version="18.2.0" -> React 18.2.0 dependencies

• "express", depth=2 -> Express + its production deps' dependencies

Get the README content of an npm package.

Returns the package's README markdown content, which typically includes installation instructions, usage examples, API documentation, and configuration options.

Args:

• package_name (string): The npm package name

Returns: README content in markdown format. Large READMEs are truncated to 25000 characters with a notice.

Examples:

• "zod" -> Zod README with schema validation examples

• "express" -> Express README with routing examples

Check whether an npm package ships TypeScript type definitions.

Detects bundled types from three sources (in priority order):

1. types field

2. typings field

3. exports map with a types condition (modern conditional exports)

Also checks for a DefinitelyTyped (@types/) companion package when no bundled types are found, and surfaces typesVersions (TS-version-specific type maps) when present.

Args:

• package_name (string): The npm package name

• version (string, optional): Specific version to check (defaults to latest)

Returns markdown with:

• Whether bundled types are present and which field declared them

• Type-definitions entry path

• Number of subpaths typed via exports (when applicable)

• Whether a typesVersions map is declared

• Whether @types/ exists on DefinitelyTyped, plus its latest version

• An install command when @types is needed

Examples:

• "express" -> @types/express on DefinitelyTyped

• "zod" -> Bundled types (TypeScript-first library)

• "react" -> Bundled types via exports/types condition

Get quality, popularity, and maintenance scores for an npm package from npms.io.

Provides detailed metrics including download counts, GitHub stars, test coverage indicators, and release frequency.

Args:

• package_name (string): The npm package name

Returns: Comprehensive scoring breakdown:

• Overall score (0-100%)

• Quality score: carefulness, tests, health, branding

• Popularity: community interest, downloads, dependents

• Maintenance: release frequency, commit frequency, open issues

• GitHub stats: stars, forks, issues

• Download statistics

Examples:

• "react" -> High scores across all categories

• "lodash" -> Well-maintained with high popularity