
Layercheck
io.github.CloudCorpRecords由 GitHub 帳號 CloudCorpRecords 發布v0.1.0更新於 Nov 3, 2026
Dockerfile 層與浪費分析器:按從大到小顯示層大小,並帶有確定性的浪費標記。
AI 翻譯由 AI 模型根據下方的原文描述翻譯,可能有誤。
原文描述
Dockerfile layer and waste analyzer: layer sizes biggest first, with deterministic waste flags.
概覽
Layercheck 的本機 MCP 服務;無需登入;STDIO。
暫無 AI 概覽:以下資訊來自註冊中心條目和服務本身。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Layercheck,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
layercheck
Every RUN, COPY, and ADD in a Dockerfile leaves a layer in the image, and layers are where image size and build-cache pain live. layercheck reads a Dockerfile as plain text — no docker daemon, no build — and reports what it finds:
- every instruction, parsed with
\continuations joined and blank lines and#comments skipped, each marked with whether it produces a layer - the layer count, and — when you supply per-layer sizes
(as
docker historyreports them) — the total size and the layers ranked biggest first, so the fattest layer is the first thing you see - deterministic waste flags, each with the line it fires on:
CONSECUTIVE_RUN— a RUN immediately after another RUN; the two could be one layerBROAD_COPY_EARLY— aCOPY . .(or./) placed before the dependency install step, busting its cache on every source changeAPT_LEFTOVER—apt-get installwithout removing/var/lib/apt/listsin the same RUNADD_LOCAL— ADD used for an ordinary local file, where COPY is the clearer instruction (remote URLs and archives are fine)
If the supplied sizes do not line up with the number of layer-producing instructions, layercheck says so and names both counts instead of silently misaligning them.
CLI
sizes.json is a JSON array of numbers: the size in bytes
of each layer-producing instruction, in Dockerfile order.
The analysis is printed as one JSON object:
{layer_count, total_size_bytes, instructions, biggest_layers, waste_flags}.
Exit codes: 0 on success, 1 on a runtime error
(including an unreadable file or a sizes length mismatch),
2 on a usage error.
MCP server
MCP client config:
Tools
analyze_dockerfile_layers— Analyze a Dockerfile's layers and flag wasted ones.dockerfile(string, required) — the Dockerfile textlayer_sizes(array of numbers, optional) — size in bytes of each layer-producing instruction, in Dockerfile order; its length must equal the number of layer-producing instructions
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
來源:README.md,提交 010d19d
工具
0版本歷史
1- v0.1.0最新Nov 3, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分