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

Muse Code · E-commerce

How to Use npm package details in Muse Code

Returns npm package metadata, including its description, maintainers, published versions, and distribution tags. Use it for a package overview before inspecting one release.

Prompts to try with npm package details in Muse Code

Copy an example into Muse Code, or ask in your own words.

Use npm package details to inspect zod and update our dependency notes with its description, repository, and published versions.

npm package detailsMuse Code
Try asking
  • Use npm package details to look this up and give me the result as a table. Save the result in ./assets.

  • Pull the latest numbers from npm package details and tell me what changed since last week.

  • Check npm package details and summarize what you find in three bullet points.

  • Pull the newest data from npm package details and give me the result as a table.

How to set up npm package details 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 npm package details

    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": "npmjs-com/packages/get_package",
        "input": {
          "url": "<url>"
        }
      }'

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

npm package details providers and prices

Spiral runs npm package details through Alexandria. Open a card for today's price, with every fee included.

AlexandriaE-commerce
npm · Get package
npmjs-com/packages/get_package

Settings you can ask for

Ask Muse Code for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Include readmeon or off

Also return the README markdown (often tens of KB).

Include versionson or off

Also return versions[] (one entry per published version; thousands for long-lived packages).

Every API field of npm · Get package is on its tool page: open its card above.

What can you do with npm package details in Muse Code?

Produce an npm dependency review tied to your project's requirements. Turn returned package metadata, discovery results, or download measurements into evidence for the review.

Compare dependency candidates

Find package names for schema validation, inspect published metadata and release requirements, and compare download totals, daily patterns, and version shares. Build a shortlist for a project trial.

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.

Review a publisher's public catalog

Inventory an npm organization's packages, use search and name suggestions to locate packages of interest, and inspect their descriptions and repositories. Produce a catalog organized by purpose.

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.

Check package references in developer documentation

Resolve package names with search and suggestions, check publisher catalogs, and inspect package and release metadata. Use the results to correct package references and dependency requirements in a tutorial.

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.

Check package identity before evaluation

Resolve a partial package name, compare search matches with publisher listings, and inspect repository and release metadata. Produce an identity check before testing the package.

Questions about npm package details in Muse Code

Can Muse Code use npm package details?

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

How much does npm package details cost in Muse Code?

$0.00873 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 npm package details in Muse Code?

No. Spiral runs npm package details on its own Alexandria account. You sign in to Spiral once and never paste a key.

How long does it take to set up npm package details in Muse Code?

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

Does Muse Code wait while npm package details runs?

npm package details runs in the background. Muse Code 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.

Get started

Start using npm package details 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