How to Use deps.dev package dependents in Cline
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.
Prompts to try with deps.dev package dependents in Cline
Copy an example into Cline, or ask in your own words.
Use deps.dev package dependents for lodash 4.17.21 on npm and add its total, direct, and indirect public dependent counts to our dependency review.
Use deps.dev package dependents to look this up and give me the result as a table. Save the result in ./assets.
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 Cline
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the server
In the Cline panel, click the MCP Servers icon and open the Remote Servers tab. Enter:
cline mcp add spiral https://api.spiral.ai/mcp --transport http --yes
- Sign in
Open the Configure tab and click Authenticate on the Spiral server. Sign in to Spiral, pick the organization and click Authorize. No API key.
- Check it
Spiral shows as connected on the Configure tab. In the CLI:
cline config mcp
Use the Spiral skill
- Send Cline this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run deps.dev package dependents
One request; the result comes back by polling or a webhook.
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: Cline finds deps.dev package dependents on Spiral, shows the price and runs it.
deps.dev package dependents providers and prices
Spiral runs deps.dev package dependents through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Cline for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Registry | npm, pypi, crates, or maven | Which registry the name belongs to: npm (registry.npmjs.org), pypi (pypi.org), crates (crates.io) or maven (Maven Central). | |
| Sample | 0 to 100 | 20 | crates only: how many dependent crates to list by name (0 to 100). |
Every API field of Package registries · Dependents is on its tool page: open its card above.
What can you do with deps.dev package dependents in Cline?
Build a dependency review table that connects packages in your project with registry evidence. A coding agent can compare current records, release histories, download activity, or public dependent counts with the versions your project uses.
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.
More on deps.dev package dependents and Cline
Overview
deps.dev package dependents in other agents
Questions about deps.dev package dependents in Cline
Can Cline use deps.dev package dependents?
Yes. Add Spiral to Cline as an MCP server, and Cline can find and run deps.dev package dependents like any built-in tool.
How much does deps.dev package dependents cost in Cline?
$0.001746 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Cline plan is separate.
Do I need an Alexandria account to use deps.dev package dependents in Cline?
No. Spiral runs deps.dev package dependents on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up deps.dev package dependents in Cline?
About two minutes: add the server, then sign in, then check it.
Does Cline wait while deps.dev package dependents runs?
deps.dev package dependents runs in the background. Cline 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.
Start using deps.dev package dependents in Cline
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Cline:
set up https://spiral.ai/SKILL.md


