mcpField
D
deps-dev

deps-dev

github.com/trancong12102Development7151 installsUpdated 6w ago
Repository

About deps-dev

deps-dev is a skill for looking up public open-source package versions through deps.dev, intended for developers adding or updating dependencies. Its script checks latest stable versions across several ecosystems in batches and reports deprecated packages.

Key features

  1. 01Look up packages across six ecosystems
  2. 02Fetch latest stable versions in batches
  3. 03Check whether packages are deprecated
  4. 04Return results in TSV format

Use cases

  1. 01Check a package version before adding a dependency
  2. 02Update a project's dependency files
  3. 03Check whether dependencies are deprecated
  4. 04Compare versions for multiple packages

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/trancong12102/agentskills --skill deps-dev

After installing, type/deps-devin Claude Code to confirm it loaded.

Bundled filesscripts/get-versions.py

Details

From the project README

Latest Package Version Lookup

Query the deps.dev API to get the latest stable version of open-source packages. This is faster and more reliable than searching the web or guessing version numbers, and it catches deprecated packages before you install them.

Supported Ecosystems

EcosystemSystem IDExample Package
npmnpmexpress, @types/node
PyPIpypirequests, django
Gogogithub.com/gin-gonic/gin
Cargocargoserde, tokio
Mavenmavenorg.springframework:spring-core
NuGetnugetNewtonsoft.Json

When to Use

  • Adding a new dependency and need the current version
  • Updating package.json, requirements.txt, Cargo.toml, etc. to latest
  • Checking whether a package has been deprecated
  • Comparing versions across multiple packages at once

When NOT to Use

  • Private or internal packages (deps.dev only indexes public registries)
  • Looking up documentation or usage examples (use context7 instead)

Workflow

DO NOT read script source code. Run scripts directly and use --help for usage.

  1. Identify the ecosystem from project files:

    • package.json or node_modules → npm
    • requirements.txt, pyproject.toml, setup.py → pypi
    • go.mod, go.sum → go
    • Cargo.toml → cargo
    • pom.xml, build.gradle → maven
    • *.csproj, packages.config → nuget

  2. Run the script:

python3 scripts/get-versions.py <system> <pkg1> [pkg2] ...

Run python3 scripts/get-versions.py --help if unsure about usage.

Examples

python3 scripts/get-versions.py npm express lodash @types/node
python3 scripts/get-versions.py pypi requests django flask
python3 scripts/get-versions.py go github.com/gin-gonic/gin

Output Format

TSV with header. One line per package:

package version published status
express 5.0.0 2024-09-10 ok
lodash 4.17.21 2021-02-20 ok

Status values: ok, deprecated, not found, error: <detail>.

Rules

  • Use the script instead of manual curl — it handles URL encoding (especially for scoped npm packages like @types/node) and fetches multiple packages in parallel, so it's both easier and faster.
  • Flag deprecated packages — if the status column says deprecated, tell the user and suggest an alternative if you know one.
  • Batch lookups when possible — the script accepts multiple package names in one call, which is faster than running it once per package.

Comments

Markdown supported