Wisco Labs: developer tools

dev.wiscolabs由 wiscolabs.dev 发布官方发布者v1.0.1更新于 Nov 5, 2026

Check PyPI and npm upgrades: known vulnerabilities, the safe version, and what each upgrade breaks.

已验证Streamable HTTP可网页运行开发者工具安全与监控

概览

AI 生成的概览

解答 PyPI 与 npm 包升级问题：已知漏洞、最小安全版本，以及每次升级会破坏什么。

可以做什么
  • 检查项目的依赖文件（requirements.txt、pip freeze、package-lock.json、package.json），找出恶意包、存在漏洞的版本和会破坏兼容的升级，并按优先级排序
  • 查询某个确切版本是否受已知安全公告影响，给出 CVE 编号、严重程度和最小安全升级版本
  • 对比单个包在两个版本之间的变化，说明哪些功能被破坏、移除或弃用，并给出整体升级风险
  • 检查 npm peer 依赖、Node.js engines 支持、各平台原生二进制，以及目标 Python 版本或平台是否有预编译 wheel
  • 检查 TypeScript 类型声明与 @types 包，并获取最新版本、仓库地址和发布说明来源
适用场景
适合在为 Python 或 JavaScript 项目规划依赖升级或安全审计时使用，尤其是在迁移到新的 Node.js 或 Python 版本、Alpine、ARM、Lambda 等新平台，或升级主要框架之前。
运行要求
远程 streamable HTTP 端点；未声明任何软件包、环境变量或请求头。需要由助手提供依赖文件内容或包名与版本。
安装前请注意
结果来自第三方收集的发布记录、发布说明和 OSV 数据，升级与漏洞建议仅供参考，应用前应自行核实。粘贴的依赖文件内容会发送到该远程服务。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Wisco Labs: developer tools，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/dev.wiscolabs%2Fdeveloper-tools/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "wisco-labs-developer-tools": {
      "type": "http",
      "url": "https://api.wiscolabs.dev/mcp/dev"
    }
  }
}

工具

9

vulnerabilities

Known vulnerabilities in a package version

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 the smallest safe upgrade.

输入参数name必填version必填ecosystem

upgrade_check

Check a whole project's dependencies

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 malicious packages and versions with known vulnerabilities (with the smallest safe version to move to, preferring a low-risk patch), then reports what each upgrade breaks, removes, or deprecates, ranked into remove_now / fix_now / no_fix_available / upgrade_first / safe / review / needs_care.

输入参数limitecosystemrequirements必填

what_changed

What changed between two versions of a package

What breaks, gets removed, is deprecated, or gains a security fix when upgrading one package between two versions, with an overall upgrade risk.

输入参数to必填from必填name必填limitecosystem

peer_check

Will my npm packages accept this upgrade? (peer dependencies)

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 installed version accept the new version, and if not, the smallest release that does, with that upgrade's risk. Also checks the new version's own peer requirements against what's installed. Answers the questions behind npm's ERESOLVE errors without running npm.

输入参数limitupgrade必填requirements必填

wheel_check

Will pip find prebuilt wheels for this platform?

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 Python version). Without one, pip builds from source, which usually fails without a compiler for packages with C extensions. For each that's missing, gives the nearest newer version that has a wheel, with that upgrade's risk.

输入参数limitpython必填platform必填requirements必填

node_check

Will my npm dependencies run on this Node.js version?

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 each that doesn't support the target, gives the smallest newer release that does, with that upgrade's risk. Works from a package-lock.json without installing anything.

输入参数node必填limitrequirements必填

native_check

Will my npm dependencies install on this platform without compiling?

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 the target platform. For those that would compile from source (needing a C/C++ toolchain and Python) or fail, gives the nearest newer version that ships a prebuilt for that platform, with that upgrade's risk.

输入参数limitplatform必填requirements必填

types_check

Which npm dependencies need @types packages, and which version?

For a TypeScript project: which dependencies ship their own type declarations, which need a DefinitelyTyped @types package (and the version that matches the installed library), and which installed @types packages describe a different major version than the library.

输入参数requirements必填

package_info

Basic facts about a package

Latest and latest stable version, repository, release count, and where its release notes come from.

输入参数name必填ecosystem

版本历史

2
  1. v1.0.1最新Nov 5, 2026
  2. v1.0.0Nov 4, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库，或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用，因此这里不要求许可证。此检查项不计入百分比。