package-version-lookup

To find the latest stable package version, the Skill queries official registries like npm, PyPI, and crates.io, defaulting to stable releases and avoiding pre-releases unless explicitly requested.

Yes, you can verify package versions across multiple ecosystems including npm, PyPI, crates.io, Go, and RubyGems, ensuring accurate dependency audits regardless of your project's language.

Multi-source verification cross-checks package versions across different registries to resolve conflicts, ensuring you never guess a version and only apply officially verified dependency updates.

The Skill provides guidance on when to pin a package version versus allowing upgrades, helping you manage dependency stability and security during project audits or new additions.

No, the package version lookup process defaults to the latest stable releases and avoids pre-release versions entirely unless you specifically request them during the dependency update.

The best way to audit project dependencies is to fetch the latest stable versions from official registries and verify them across multiple sources, guiding updates without guessing.