cloud.coredls.vigia/vigia

Tools

• check_dependencies

  Evaluates a full package.json (npm) or requirements.txt (pypi): for each dependency returns the latest version, whether the declared range includes it (up_to_date / outdated / outdated_major), whether the package is deprecated, and known vulnerabilities (OSV IDs) of the lowest version the range allows. Use when opening a project or before upgrading dependencies.

  shallow
• find_compatible_version

  Finds the newest stable version of an npm or PyPI package that works with the given runtime/peer versions, using the engines, peerDependencies or Requires-Python declared by EACH version. Use when a project is pinned to an older Node, React, TypeScript or Python and the latest version may not support it.

  shallow
• find_package

  Finds packages or models by name prefix, ordered by popularity. Use when the exact name is unknown.

  shallow
• model_info

  Price per million tokens, context window, max output and retirement date of AI models (OpenRouter catalog). Use before writing a model ID in code or estimating costs. With model_id returns one model; with provider or query returns a list.

  shallow
• package_status

  Latest stable version, publish date, deprecation/yank status, runtime requirements (engines/python), peer dependencies, license and advisories of an npm or PyPI package. Use before recommending, installing or pinning a package version.

  shallow
• recent_changes

  Latest detected changes: new releases, deprecations, removed packages, AI model price changes or retirement announcements. Optionally filtered to one package or model.

  shallow
• symbol_status

  Checks whether an exported function/class/type (or Class.member) exists in a specific version of an npm package, its exact signature, which module path to import it from, and whether it is deprecated (with the deprecation message). Use before writing code that calls a library API you are not 100% sure about for the version in use. Default version: latest.

  shallow
• upgrade_impact

  What changes when upgrading an npm package from one version to another: removed exports and modules, changed function signatures and class members, newly deprecated APIs, changed engines/peerDependencies, and changelog sections in between. Computed from the TypeScript types of both versions. Use BEFORE upgrading a dependency or when code written for an older version fails on a newer one. Versions can be exact ("14.2.3") or a major ("14"); "to" defaults to latest.

  shallow
• version_status

  For one exact version of an npm or PyPI package: whether it exists, when it was published, whether it was deprecated/yanked, how far behind latest it is, its known vulnerabilities (OSV) and the nearest version that fixes all of them. Use before keeping, pinning or recommending a specific version, or when auditing a lockfile entry.

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/588dcb75-852e-4c04-9f1f-cd2976e91e9a/badge.svg)](https://vouch.tools/servers/588dcb75-852e-4c04-9f1f-cd2976e91e9a)