Enginedrift

io.github.CloudCorpRecords由 GitHub 账号 CloudCorpRecords 发布v0.1.0更新于 Nov 3, 2026

在构建被破坏之前,检测 package.json、CI 配置和 Dockerfile 之间的 Node 引擎版本偏差。

AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。

原文描述

Detect Node engine drift across package.json, CI config, and Dockerfile before it breaks a build.

已验证STDIO仅桌面

概览

Enginedrift 的本地 MCP 服务;无需登录;STDIO。

暂无 AI 概览:以下信息来自注册中心条目和服务本身。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Enginedrift,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

enginedrift

Three places in a Node project quietly name a Node version: engines.node in package.json, the node-version values in CI, and the FROM node:... tags in a Dockerfile. When they disagree, the failure usually shows up late — a CI job running a different major than the container, or a syntax feature that works in one place and not another. enginedrift extracts what each source actually declares and reports the drift up front.

It answers with:

  • drift — true when sources declare conflicting majors, or a source sits entirely below package.json's declared minimum
  • sources — one entry per provided source, with the raw declared strings, the majors found (ascending, unique), and a note when a source cannot pin a major (for example a CI node-version-file key)
  • issues — in a fixed order: MAJOR_MISMATCH (distinct majors across sources), BELOW_MINIMUM (a source entirely below package.json's minimum major), UNPINNED_IMAGE (a Dockerfile FROM node with no numeric tag, such as lts-alpine or latest), and NO_ENGINES (package.json declares no engines.node)

Extraction notes: for an engines range, the declared minimum is the smallest major mentioned (>=20 means 20, ^18.2 means 18, 20.x means 20, and a bare * declares nothing). CI values may be scalars, inline matrix lists such as [20, 22], or YAML block lists under the key. Every Dockerfile stage is scanned, so multi-stage builds report each FROM node line. An absent CI config or Dockerfile is never an issue by itself. Pure local computation: no network, no configuration, no files read by the tool itself.

CLI

bash
npx @reneturcios/enginedrift check --package-json package.json --ci .github/workflows/ci.yml --dockerfile Dockerfilenpx @reneturcios/enginedrift --version

The --ci and --dockerfile flags are optional. The result is printed as JSON. Exit codes: 0 when the check ran (drift is data, not an error), 1 on a runtime error (including an unreadable file or an invalid package.json), 2 on a usage error.

MCP server

bash
npx -y @reneturcios/enginedrift mcp

MCP client config:

json
{  "mcpServers": {    "enginedrift": {      "command": "npx",      "args": ["-y", "@reneturcios/enginedrift", "mcp"]    }  }}

Tools

  • check_engine_drift — Compare Node majors declared in package.json, CI config, and a Dockerfile, and report drift.
    • package_json (string, required) — package.json text; its engines.node range is the anchor source
    • ci_yaml (string, optional) — CI workflow YAML text; node-version values are extracted
    • dockerfile (string, optional) — Dockerfile text; FROM node image tags are extracted

Docker

bash
docker run -i ghcr.io/cloudcorprecords/enginedriftdocker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/enginedrift check --package-json /w/package.json --dockerfile /w/Dockerfile

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # tsx --test test/*.test.ts (pure local, no network)npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios

来源:README.md,提交 d1a41b7

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.0最新Nov 3, 2026

评分

已满足适用检查项的 50%

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

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分