Wisco Labs: developer tools

• vulnerabilities — Is this exact version of a package affected by known security advisories? Returns each vulnerability (with CVE ids and severity), the versions that fix it, and
• upgrade_check — Give it a project's dependencies: a requirements.txt or pip freeze output for Python, or a package-lock.json, package.json, or name@version lines for npm. Flags
• what_changed — What breaks, gets removed, is deprecated, or gains a security fix when upgrading one package between two versions, with an overall upgrade risk.
• peer_check — Before upgrading a core npm package (react, typescript, eslint, vite...), checks every dependency in the project that declares it as a peer dependency: does the
• wheel_check — For each pinned Python package, whether a prebuilt wheel exists for a target Python version and platform (Windows ARM, Alpine/musl, Linux ARM, macOS, a new Pyth
• node_check — Before moving a project to a new Node.js version (e.g. off Node 20 to 22 or 24), checks each npm dependency's declared Node support (its engines field). For eac
• native_check — Before building on Alpine, Linux ARM, Windows ARM, a Mac or Lambda, checks which npm dependencies contain native code and whether a prebuilt binary exists for t
• types_check — For a TypeScript project: which dependencies ship their own type declarations, which need a DefinitelyTyped @types package (and the version that matches the ins
• package_info — Latest and latest stable version, repository, release count, and where its release notes come from.

No hidden text found in the tool definitions.

Text a person reading a tool definition does not see and a model does. Invisible characters can be pasted in by accident; this says what is there, not why. Covers tools only, not prompts or resources.