[Integrations](https://spiral.ai/integrations) › [dots](https://spiral.ai/integrations/dots) › [npm package dependents](https://spiral.ai/integrations/dots/npm-package-dependents)

# How to Use npm package dependents in dots

Returns npm packages that depend on a package. Use it to discover downstream integrations and choose packages to review before a breaking change.

|  |  |
| --- | --- |
| Model | npm package dependents |
| Available through | Alexandria |
| Category | E-commerce |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with npm package dependents in dots

- Every week, use npm package dependents for fastify and highlight names newly returned since the previous report.
- Every Monday at 9am: use npm package dependents to look this up and give me the result as a table.
- Pull the latest numbers from npm package dependents and tell me what changed since last week.
- Check npm package dependents and summarize what you find in three bullet points.
- Pull the newest data from npm package dependents and give me the result as a table.

## How to set up npm package dependents in dots

Pick the way that suits you. Each takes about two minutes.

### Use the Spiral skill

1. **Send dots this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use Spiral's MCP server

1. **Create an API key**: In the console, open API keys and create a key for your dot. Copy it.

2. **Send your dot this message**: Your dot reads Spiral's skill and asks for your API key.

```text
set up https://spiral.ai/SKILL.md
```

3. **Give your dot the key**: When your dot asks for the key, add it where your dot keeps secrets, never in the chat itself.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run npm package dependents**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "npmjs-com/packages/list_dependents",
    "input": {
      "package": "<package>"
    }
  }'
```

Then paste one of the prompts above: dots finds npm package dependents on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/dots

## npm package dependents tools and prices

- [npm · List dependents](https://spiral.ai/tools/alexandria/npmjs-com/packages/list_dependents) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| cursor |  | — | `next_cursor` from a previous page (offset in items). Pattern: ^[0-9]+$. |

## What can you do with npm package dependents in dots?

Keep a weekly npm package watchlist with changes worth reviewing. Compare successive results to highlight changes in public package records or download measurements.

### Plan a major version migration

Review release requirements and downstream packages alongside download totals, daily trends, and version shares. Use the evidence to choose compatibility tests and prioritize migration documentation.

### Prepare a weekly package review

Compare saved publisher listings, package metadata, release details, and returned dependent names. Add changes in download totals, daily patterns, and version shares to identify items worth reviewing.

### Find downstream integrations

Start with dependent packages and publisher catalogs, then use search and name suggestions to find related integrations. Review descriptions and download totals to select packages for compatibility testing.

### Research package adoption

Define a package sample through search and publisher listings. Compare download totals, daily trends, version shares, and downstream package relationships for an adoption report.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All dots guides](https://spiral.ai/integrations/dots)

## npm package dependents in other agents

- [Amp](https://spiral.ai/integrations/amp/npm-package-dependents)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/npm-package-dependents)
- [Claude](https://spiral.ai/integrations/claude-desktop/npm-package-dependents)
- [Claude Code](https://spiral.ai/integrations/claude-code/npm-package-dependents)
- [Cline](https://spiral.ai/integrations/cline/npm-package-dependents)
- [Codex](https://spiral.ai/integrations/codex/npm-package-dependents)
- [Cursor](https://spiral.ai/integrations/cursor/npm-package-dependents)
- [Devin](https://spiral.ai/integrations/devin/npm-package-dependents)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/npm-package-dependents)
- [Gemini](https://spiral.ai/integrations/gemini/npm-package-dependents)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/npm-package-dependents)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/npm-package-dependents)
- [goose](https://spiral.ai/integrations/goose/npm-package-dependents)
- [Grok](https://spiral.ai/integrations/grok/npm-package-dependents)
- [Grok Build](https://spiral.ai/integrations/grok-build/npm-package-dependents)
- [Hermes](https://spiral.ai/integrations/hermes/npm-package-dependents)
- [Instinct](https://spiral.ai/integrations/instinct/npm-package-dependents)
- [Manus](https://spiral.ai/integrations/manus/npm-package-dependents)
- [Muse](https://spiral.ai/integrations/muse/npm-package-dependents)
- [Muse Code](https://spiral.ai/integrations/muse-code/npm-package-dependents)
- [n8n](https://spiral.ai/integrations/n8n/npm-package-dependents)
- [Notion](https://spiral.ai/integrations/notion/npm-package-dependents)
- [OpenClaw](https://spiral.ai/integrations/openclaw/npm-package-dependents)
- [opencode](https://spiral.ai/integrations/opencode/npm-package-dependents)
- [Perplexity](https://spiral.ai/integrations/perplexity/npm-package-dependents)
- [Raycast](https://spiral.ai/integrations/raycast/npm-package-dependents)
- [VS Code](https://spiral.ai/integrations/vscode/npm-package-dependents)
- [Windsurf](https://spiral.ai/integrations/windsurf/npm-package-dependents)
- [Zapier](https://spiral.ai/integrations/zapier/npm-package-dependents)

## More dots guides

- [npm downloads by version](https://spiral.ai/integrations/dots/npm-downloads-by-version)
- [npm package details](https://spiral.ai/integrations/dots/npm-package-details)
- [npm daily package downloads](https://spiral.ai/integrations/dots/npm-daily-package-downloads)
- [npm package download totals](https://spiral.ai/integrations/dots/npm-package-download-totals)
- [mydealz store vouchers](https://spiral.ai/integrations/dots/mydealz-store-vouchers)
- [npm package name suggestions](https://spiral.ai/integrations/dots/npm-package-name-suggestions)

## Questions about npm package dependents in dots

**Can dots use npm package dependents?**

Yes. Add Spiral to dots as an MCP server, and dots can find and run npm package dependents like any built-in tool.

**How much does npm package dependents cost in dots?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your dots plan is separate.

**Do I need an Alexandria account to use npm package dependents in dots?**

You need no Alexandria account. dots uses one Spiral API key for every tool, and Spiral runs npm package dependents on its own Alexandria account.

**How long does it take to set up npm package dependents in dots?**

About two minutes: create an API key, then send your dot this message, then give your dot the key.

**Does dots wait while npm package dependents runs?**

npm package dependents runs in the background. dots starts the run, checks on it and gives you the json when it's ready.

**How fresh are npm download statistics?**

npm documents a daily process that aggregates the previous day's logs after UTC midnight. Download statistics therefore describe completed reporting days.

**Why might a published package be missing from npm search?**

npm says newly published packages can take up to two weeks to appear. Deprecated packages are excluded from search results.

**Do npm download counts represent unique users?**

No. npm counts successful package tarball responses, including downloads from automated builds, mirrors, and analysis robots.

**How much download history can npm return at once?**

npm limits download queries other than bulk queries to 18 months per request. Per-version download counts cover only the previous seven days.

**Does npm search return every match in one response?**

npm registry search returns at most 250 matches per request and supports offset pagination. The response also reports a total.

