[Integrations](https://spiral.ai/integrations) › [Manus](https://spiral.ai/integrations/manus) › [deps.dev package version history](https://spiral.ai/integrations/manus/deps-dev-package-version-history)

# How to Use deps.dev package version history in Manus

Get known package versions with available publication times, the default-release flag, and deprecation status. Use the history to compare release cadence or review upgrade candidates beyond the current release.

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

## Prompts to try with deps.dev package version history in Manus

- Use deps.dev package version history for pandas on PyPI. Show the ten most recently published releases with dates and any deprecation flags.
- Use deps.dev package version history for com.google.guava:guava on Maven. Show recent publication dates and identify the release marked as the default.
- Use deps.dev package version history to look this up and give me the result as a table.
- Pull the latest numbers from deps.dev package version history and tell me what changed since last week.
- Check deps.dev package version history and summarize what you find in three bullet points.

## How to set up deps.dev package version history in Manus

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

### Use the Manus connector

1. **Add a custom MCP connector**: In Manus open Settings › Connectors (or the connectors icon under the chat box), then Add connectors › Custom MCP and Add MCP by URL. Name it Spiral, set Transport to HTTP and paste this Server URL:

```text
https://api.spiral.ai/mcp
```

2. **Sign in to Spiral and approve**: Manus asks you to sign in the first time it uses Spiral. Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Manus never sees it, and you can remove it under Settings › Connected apps in the console.

### Use the Spiral skill

1. **Send Manus 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.

```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 version history**: 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/versions",
    "input": {
      "name": "<name>",
      "registry": "npm"
    }
  }'
```

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

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

## deps.dev package version history tools and prices

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

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| limit | 1 to 200 | 50 | Versions per page, 1 to 200. |
| offset | 0 to 100000 | 0 | Versions to skip, newest first. Page by passing the previous response's next_offset. |

## What can you do with deps.dev package version history in Manus?

Compare public packages in a table with dated evidence for a library decision. A chat app can explain registry metadata, release activity, downloads, or public dependent counts without treating those measures as interchangeable.

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

### Document dependency upgrade candidates

Create a review table for public dependencies with current releases, publication dates, license metadata, project links, and known deprecated versions.

### Investigate download spikes

Compare daily downloads for pandas with its publication timeline to identify spikes that coincide with releases and spikes that need another explanation.

### 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 Manus guides](https://spiral.ai/integrations/manus)

## deps.dev package version history in other agents

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

## More Manus guides

- [deps.dev package dependents](https://spiral.ai/integrations/manus/deps-dev-package-dependents)
- [npm, PyPI and crates.io downloads](https://spiral.ai/integrations/manus/npm-pypi-and-crates-io-downloads)
- [arXiv subject sets](https://spiral.ai/integrations/manus/arxiv-subject-sets)
- [npm, PyPI, crates.io and Maven package details](https://spiral.ai/integrations/manus/npm-pypi-crates-io-and-maven-package-details)
- [arXiv paper search](https://spiral.ai/integrations/manus/arxiv-paper-search)
- [xAI API release notes](https://spiral.ai/integrations/manus/xai-api-release-notes)

## Questions about deps.dev package version history in Manus

**Can Manus use deps.dev package version history?**

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

**How much does deps.dev package version history cost in Manus?**

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

**Do I need an Alexandria account to use deps.dev package version history in Manus?**

No. Spiral runs deps.dev package version history 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 version history in Manus?**

About two minutes: add a custom MCP connector, then sign in to Spiral and approve.

**Does Manus wait while deps.dev package version history runs?**

deps.dev package version history runs in the background. Manus 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.

