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

# How to Use deps.dev package dependents in dots

Get total, direct, and indirect counts of public packages that depend on a specific package version. Use these counts to compare a release's ecosystem reach, separately from download activity.

|  |  |
| --- | --- |
| Model | deps.dev package dependents |
| Available through | Alexandria |
| Category | Developer |
| Price | $0.001746 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with deps.dev package dependents in dots

- Once a week, use deps.dev package dependents for lodash 4.17.21 on npm. Compare its total, direct, and indirect public dependent counts with the previous review.
- Every Monday at 9am: use deps.dev package dependents to look this up and give me the result as a table.
- Pull the latest numbers from deps.dev package dependents and tell me what changed since last week.
- Check deps.dev package dependents and summarize what you find in three bullet points.
- Pull the newest data from deps.dev package dependents and give me the result as a table.

## How to set up deps.dev 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 deps.dev 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": "package-registry-metadata-download-stats/packages/dependents",
    "input": {
      "name": "<name>",
      "registry": "npm"
    }
  }'
```

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

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

## deps.dev package dependents tools and prices

- [Package registries · Dependents](https://spiral.ai/tools/alexandria/package-registry-metadata-download-stats/packages/dependents) (Alexandria): $0.001746 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| sample | 0 to 100 | 20 | crates only: how many dependent crates to list by name (0 to 100). |
| version |  | — | Exact version to count dependents for, e.g. 5.1.0 or 33.4.8-jre. Default: the registry's default (latest) version. |

## What can you do with deps.dev package dependents in dots?

Produce a recurring package review for a fixed watchlist such as react, requests, and serde. A scheduled agent can compare successive registry results and report changes in releases, deprecation flags, download activity, or public dependent counts.

### Compare library candidates

Review axios and got on npm using current package details, release histories, daily downloads, and version-specific dependent counts. Keep download activity and public package adoption as separate columns.

### Prepare a support retirement review

For an older release of requests, assemble its publication date and deprecation status, public dependent counts, current package record, and recent package download trend. Use the evidence to frame a support discussion.

### Prepare an open-source funding brief

Build a review of serde or tokio with project links, release cadence, download activity, and public dependent counts. Give reviewers concrete evidence for choosing projects to support.

### Review activity around a release

Place a package's release dates beside daily downloads, its current record, and dependent counts for selected versions. Report changes around the release without attributing package-wide downloads to that version.

### Compare Java package footprints

Review com.google.guava:guava and org.apache.commons:commons-lang3 using package descriptions, project links, release histories, and public dependent counts for selected versions.

## Overview

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

## deps.dev package dependents in other agents

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

## More dots guides

- [arXiv subject sets](https://spiral.ai/integrations/dots/arxiv-subject-sets)
- [deps.dev package version history](https://spiral.ai/integrations/dots/deps-dev-package-version-history)
- [arXiv paper search](https://spiral.ai/integrations/dots/arxiv-paper-search)
- [npm, PyPI and crates.io downloads](https://spiral.ai/integrations/dots/npm-pypi-and-crates-io-downloads)
- [arXiv paper details](https://spiral.ai/integrations/dots/arxiv-paper-details)
- [npm, PyPI, crates.io and Maven package details](https://spiral.ai/integrations/dots/npm-pypi-crates-io-and-maven-package-details)

## Questions about deps.dev package dependents in dots

**Can dots use deps.dev package dependents?**

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

**How much does deps.dev package dependents cost in dots?**

$0.001746 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 deps.dev package dependents in dots?**

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

**How long does it take to set up deps.dev 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 deps.dev package dependents runs?**

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

**Does the data include private package usage?**

deps.dev counts only public dependents. Its counts describe the visible package ecosystem, so they cannot establish how many private applications use a package.

**How quickly does package data update?**

deps.dev says commonly used packages are usually current within about an hour, while inactive packages can have older data. npm processes download logs once daily shortly after midnight UTC.

**Are package publication dates always available?**

No. deps.dev returns publication timestamps when they are available from the package registry.

**What does the default release mean?**

In deps.dev, it identifies the release installed when no version is specified. Use that flag when your question concerns the default installation.

**Can the release history identify deprecated versions?**

deps.dev version records include a deprecation flag. That identifies a release marked as deprecated, rather than establishing whether every older release should be replaced.

