Find the latest package versions from official registries. Use when adding new packages to dependency files, updating existing package versions, or before suggesting any package installation.
This skill provides guidance for finding accurate package version information before adding or updating dependencies. Default to the latest stable version unless the user has explicitly specified a particular version.
Use context7_resolve-library-id to find the Context7-compatible library ID, then use context7_query-docs to get version information.
Best for: Libraries with comprehensive documentation (e.g., Next.js, React, FastAPI)
Use webfetch to scrape version information directly from official package registries:
| Ecosystem | Registry URL |
|---|---|
| npm/Node.js | https://www.npmjs.com/package/{package-name} |
| Python (PyPI) | https://pypi.org/project/{package-name}/ |
| Rust (crates.io) | https://crates.io/crates/{package-name} |
| Go | https://pkg.go.dev/{package-path} |
| Ruby (RubyGems) | https://rubygems.org/gems/{package-name} |
| PHP (Packagist) | https://packagist.org/packages/{vendor}/{package} |
Best for: Quick lookups when the package registry page is reliable
If the above methods fail, search for "{package name} latest version" or visit the package's GitHub releases page.
Best for: Niche packages or when registry pages are blocked
User: "Add react-query to my project"
→ Use webfetch on https://www.npmjs.com/package/@tanstack/react-query
→ Extract latest version from the page
User: "Update fastapi version"
→ Use context7_resolve-library-id with "fastapi"
→ Query docs for latest version
User: "Add serde"
→ Use webfetch on https://crates.io/crates/serde
→ Extract version from the page