跳到主要内容
知仓学习社ZHICANG

cull-release-verify

Use when verifying or auditing a Cull release, DMG, updater archive, notarization, Homebrew cask, installed version, launch health, or post-publicat…

不碰外部(只输出文字)无严重或高危命中glebis/claude-skills

它会碰到什么

扫了多少2 个文本文件,2 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

Cull Release Verify

Principle

Reconstruct release truth from immutable public evidence. Verification is

read-only by default.

Verify

  1. Resolve the Cull checkout and select the explicit version or latest public

release.

  1. Run npm run release:cull -- state show --version "$VERSION" --json and parse

exactly one JSON envelope.

  1. Bind the annotated Git tag object and peeled commit to the published release,

authenticated workflow run, provenance, and required asset inventory.

  1. Download artifacts to an isolated temporary directory. Run Cull's exact

artifact verifier; check updater signature, SHA-256 checksums, DMG contents,

embedded version and architecture, codesign, Gatekeeper, and notarization

staple.

  1. Compare Homebrew version and SHA-256 with public provenance and require its

promotion evidence.

  1. Report version, commit, tag object, workflow, asset hashes, release URL, tap

commit, installed-version evidence, launch evidence, and mismatches.

Default to no installation. When the user explicitly requests an install smoke,

use an isolated location and preserve any existing app. Never edit release state,

the GitHub release, tags, the tap, system Applications, or cull.db.

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。