deps-dev

Identifies the latest stable version of a package from any supported ecosystem using the SwaggerHub API's built-in feature.

22|1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/itechmeat/llm-code --skill deps-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deps-dev
Source: https://github.com/itechmeat/llm-code/tree/main/skills/deps-dev
Command: npx skills add https://github.com/itechmeat/llm-code --skill deps-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies obtaining the correct default/latest version of a package across ecosystems by querying the deps.dev API v3 and selecting the version marked as default.

Core Features & Use Cases

  • Single-request version discovery: Fetch the default version with one HTTP call and parse the response for versions[].isDefault.
  • Ecosystem aware: Supports NPM, PYPI, MAVEN, GO, RUBYGEMS, and more; automatically handles ecosystem-specific naming and encoding.
  • Use Case: When integrating with a build or dependency-tracking tool, you can rely on a deterministic version selection to avoid manual lookup errors.

Quick Start

Query the default version for a known package (e.g., NPM package react) by calling GetPackage and returning the selected version.

Frequently Asked Questions about deps-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the default version of an NPM package using the deps.dev API?

To find the default version of an NPM package, query the deps.dev API v3 GetPackage endpoint and parse the JSON response to locate the version where the isDefault field is true. This provides deterministic version selection.

Can I look up the latest package version for multiple ecosystems like PYPI, MAVEN, and GO?

Yes, you can look up the latest package version across multiple ecosystems including PYPI, MAVEN, GO, and RUBYGEMS. The approach queries the deps.dev API v3 and applies ecosystem-specific URL encoding to retrieve the canonical default version.

How do I handle URL encoding for package names when querying the deps.dev API?

When querying the deps.dev API, you must apply proper URL encoding to package names before requesting the GetPackage endpoint. This ensures special characters in package names are correctly parsed to return the default version.

What happens if there is no explicit default version marked in the deps.dev response?

If no explicit default version is marked in the deps.dev JSON response, the process includes handling cases where the isDefault field is absent. This ensures your dependency tracking avoids manual lookup errors when a default is missing.

What is the best way to automate dependency version selection for build tools?

The best way to automate dependency version selection is using a single-request API call to deps.dev to fetch the version marked as default. This deterministic approach avoids manual lookup errors during build or dependency-tracking integration.

Does the deps.dev API v3 require any dependencies to fetch package versions?

No, the deps.dev API v3 requires no external dependencies to fetch package versions. It operates by making an HTTP call to the GetPackage endpoint and parsing the JSON output to locate the isDefault flag.