Spiral gives your agent every tool with one account. Browse the tools →

Muse Code · Developer

How to Use deps.dev package dependents in Muse Code

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 Muse Code

Copy an example into Muse Code, 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.

deps.dev package dependentsMuse Code
Try asking
  • 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 Muse Code

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

Use Spiral's MCP server

  1. Install Muse Code
    curl -fsSL https://dev.meta.ai/install.sh | bash
  2. Ask Muse to add the server

    Start muse and ask:

    Add the Spiral MCP server at https://api.spiral.ai/mcp
  3. Sign in

    In your terminal, run:

    muse mcp login spiral

Use the Spiral skill

  1. Send Muse Code 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 the Spiral CLI

  1. 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

  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.

    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: Muse Code 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.

AlexandriaDeveloper
Package registries · Dependents
package-registry-metadata-download-stats/packages/dependents

Settings you can ask for

Ask Muse Code for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Registrynpm, pypi, crates, or maven

Which registry the name belongs to: npm (registry.npmjs.org), pypi (pypi.org), crates (crates.io) or maven (Maven Central).

Sample0 to 10020

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 Muse Code?

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.

Questions about deps.dev package dependents in Muse Code

Can Muse Code use deps.dev package dependents?

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

How much does deps.dev package dependents cost in Muse Code?

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

Do I need an Alexandria account to use deps.dev package dependents in Muse Code?

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 Muse Code?

About two minutes: install Muse Code, then ask Muse to add the server, then sign in.

Does Muse Code wait while deps.dev package dependents runs?

deps.dev package dependents runs in the background. Muse Code 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.

Get started

Start using deps.dev package dependents in Muse Code

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Muse Code:

Set up Muse Code

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options