Freshcheck

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

评估依赖陈旧程度:按依赖项给出落后级别,并按从已弃用到最新的风险分组。

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

原文描述

Assess dependency staleness: behind level per dependency, grouped by risk from abandoned to current.

已验证STDIO仅桌面

概览

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

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

安装

在 SourceWeft 中

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

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

其他 MCP 客户端

参照 仓库 中的启动说明。

README

freshcheck

A dependency tree quietly ages. Some packages are a patch behind and can be bumped without a thought, some are a major version behind and need a planned upgrade, and some have not released anything in years — or their repository has been archived outright — and are a risk whatever version they are on. freshcheck takes the tree you have — each dependency's name, installed version, and latest available version, with optional abandonment signals — and sorts it into exactly those risk groups:

  • Behind level — for every dependency, current and latest are compared component by component, numerically. The first component that differs decides: major, minor, or patch. When latest is not ahead of current — equal, or even behind it — the level is none. Versions must be strict MAJOR.MINOR.PATCH semver: three numeric components, no leading zeros, no prerelease or build suffix.
  • Abandoned — a dependency counts as abandoned when its repository is archived, or when it has gone at least abandoned_days without a release (default 730, measured by the optional days_since_last_release). Abandonment outranks the version gap: an archived package two majors behind is grouped abandoned, with its behind level still reported alongside so the size of the gap is not lost.
  • Groups and counts — every dependency lands in one group — abandoned, major, minor, patch, or current (behind level none, not abandoned) — and the result carries the names in each group plus the group sizes and the overall total.

Every list in the result is sorted ascending, so the same tree always yields exactly the same assessment. Malformed input — a missing or empty dependency list, a missing, empty, or duplicate name, a version that is not strict semver, a wrongly typed signal — is a validation error naming the offending path (for example dependencies[1].latest must be a strict MAJOR.MINOR.PATCH semver version), and no partial assessment is produced. The computation is pure and local: no network, no registry lookups, no files read beyond the input you pass in — freshcheck judges only the versions and signals you supply.

CLI

bash
npx @reneturcios/freshcheck assess --input args.jsonnpx @reneturcios/freshcheck --version

args.json contains the full arguments object:

json
{  "dependencies": [    { "name": "core", "current": "2.0.0", "latest": "2.0.0" },    { "name": "lib", "current": "1.9.0", "latest": "1.10.2" },    { "name": "old", "current": "0.8.1", "latest": "3.0.0", "archived": true }  ]}

archived defaults to false per dependency, and abandoned_days defaults to 730 for the whole call. The assessment is printed as JSON:

json
{  "dependencies": [    { "name": "core", "current": "2.0.0", "latest": "2.0.0", "behind": "none", "group": "current" },    { "name": "lib", "current": "1.9.0", "latest": "1.10.2", "behind": "minor", "group": "minor" },    { "name": "old", "current": "0.8.1", "latest": "3.0.0", "behind": "major", "group": "abandoned" }  ],  "groups": {    "abandoned": ["old"],    "major": [],    "minor": ["lib"],    "patch": [],    "current": ["core"]  },  "counts": { "abandoned": 1, "major": 0, "minor": 1, "patch": 0, "current": 1, "total": 3 }}

Note lib: 1.10.2 is a minor step ahead of 1.9.0 because components compare numerically, not lexicographically.

Exit codes: 0 on success, 1 on a runtime error (including an unreadable or invalid input file, or invalid input), 2 on a usage error.

MCP server

bash
npx -y @reneturcios/freshcheck mcp

MCP client config:

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

Tools

  • assess_freshness — Assess how stale a dependency tree is, grouped by risk.

    • dependencies (array, required, at least one) — dependencies as {name, current, latest, archived?, days_since_last_release?} objects; name is unique across the set, and current / latest are strict MAJOR.MINOR.PATCH semver versions
    • abandoned_days (integer, optional, default 730, at least 1) — days without a release at which a dependency counts as abandoned

    Returns {dependencies, groups, counts}.

Docker

bash
docker run -i ghcr.io/cloudcorprecords/freshcheckdocker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/freshcheck assess --input /w/args.json

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,提交 b012cdb

工具

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

版本历史

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

评分

已满足适用检查项的 50%

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

  • 近 30 天内可连通25 分

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

  • 已声明认证方式10 分

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

  • 已列出工具15 分

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

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