How to Use deps.dev package version history in Grok
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.
Prompts to try with deps.dev package version history in Grok
Copy an example into Grok, or ask in your own words.
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 Grok
Pick the way that suits you. Each takes about two minutes.
Use the Grok connector
- Add a custom connector
In Grok open Settings › Connect Apps, then Add a custom connector. Name it Spiral, paste this URL, leave Headers empty and click Add MCP.
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Grok opens Spiral: sign in, pick the organization and click Authorize. Spiral gives the connection its own API key; Grok never sees it, and you can remove the connection under Settings › Connected apps.
- Check that it is connected
Connect Apps › Custom shows Spiral as Connected. It works in every Grok chat and Grok bot.
Use the Spiral skill
- Send Grok 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 version history
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/versions", "input": { "name": "<name>", "registry": "npm" } }'
Then paste one of the prompts above: Grok finds deps.dev package version history on Spiral, shows the price and runs it.
deps.dev package version history providers and prices
Spiral runs deps.dev package version history through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Grok 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). | |
| 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. |
Every API field of Package registries · Version history is on its tool page: open its card above.
What can you do with deps.dev package version history in Grok?
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.
More on deps.dev package version history and Grok
Overview
deps.dev package version history in other agents
Questions about deps.dev package version history in Grok
Can Grok use deps.dev package version history?
Yes. Add Spiral to Grok as an MCP server, and Grok can find and run deps.dev package version history like any built-in tool.
How much does deps.dev package version history cost in Grok?
$0.001746 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Grok plan is separate.
Do I need an Alexandria account to use deps.dev package version history in Grok?
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 Grok?
About two minutes: add a custom connector, then sign in to Spiral and approve, then check that it is connected.
Does Grok wait while deps.dev package version history runs?
deps.dev package version history runs in the background. Grok 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 version history in Grok
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Grok:
set up https://spiral.ai/SKILL.md


