clawsec-suite by prompt-security/clawsec
npx skills add https://github.com/prompt-security/clawsec --skill clawsec-suite这意味着 clawsec-suite 能够:
advisories/feed.jsonHEARTBEAT.md 中的可移植心跳工作流hooks/clawsec-advisory-guardian/scripts/scripts/guarded_skill_install.mjsscripts/discover_skill_catalog.mjs广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
clawsec-suite 不在本文档中硬编码附加技能的名称。
在运行时从权威索引 (https://clawsec.prompt.security/skills/index.json) 发现当前目录:
SUITE_DIR="${INSTALL_ROOT:-$HOME/.openclaw/skills}/clawsec-suite"
node "$SUITE_DIR/scripts/discover_skill_catalog.mjs"
备用行为:
skill.json 中的目录元数据。bash/zsh 中,保持路径变量可扩展(例如,INSTALL_ROOT="$HOME/.openclaw/skills")。'$HOME/.openclaw/skills')。$env:INSTALL_ROOT = Join-Path $HOME ".openclaw\\skills"\$HOME/...),套件脚本现在会快速失败并给出清晰的错误信息。npx clawhub@latest install clawsec-suite
set -euo pipefail
VERSION="${SKILL_VERSION:?Set SKILL_VERSION (e.g. 0.0.8)}"
INSTALL_ROOT="${INSTALL_ROOT:-$HOME/.openclaw/skills}"
DEST="$INSTALL_ROOT/clawsec-suite"
BASE="https://github.com/prompt-security/clawsec/releases/download/clawsec-suite-v${VERSION}"
TEMP_DIR="$(mktemp -d)"
trap 'rm -rf "$TEMP_DIR"' EXIT
# 固定的发布签名公钥(首次使用时通过带外方式验证指纹)
# 指纹(SPKI DER 的 SHA-256):711424e4535f84093fefb024cd1ca4ec87439e53907b305b79a631d5befba9c8
RELEASE_PUBKEY_SHA256="711424e4535f84093fefb024cd1ca4ec87439e53907b305b79a631d5befba9c8"
cat > "$TEMP_DIR/release-signing-public.pem" <<'PEM'
-----BEGIN PUBLIC KEY-----
MCowBQYDK2VwAyEAS7nijfMcUoOBCj4yOXJX+GYGv2pFl2Yaha1P4v5Cm6A=
-----END PUBLIC KEY-----
PEM
ACTUAL_KEY_SHA256="$(openssl pkey -pubin -in "$TEMP_DIR/release-signing-public.pem" -outform DER | shasum -a 256 | awk '{print $1}')"
if [ "$ACTUAL_KEY_SHA256" != "$RELEASE_PUBKEY_SHA256" ]; then
echo "ERROR: Release public key fingerprint mismatch" >&2
exit 1
fi
ZIP_NAME="clawsec-suite-v${VERSION}.zip"
# 1) 下载发布存档 + 已签名的校验和清单 + 签名公钥
curl -fsSL "$BASE/$ZIP_NAME" -o "$TEMP_DIR/$ZIP_NAME"
curl -fsSL "$BASE/checksums.json" -o "$TEMP_DIR/checksums.json"
curl -fsSL "$BASE/checksums.sig" -o "$TEMP_DIR/checksums.sig"
# 2) 在信任任何哈希值之前,验证校验和清单的签名
openssl base64 -d -A -in "$TEMP_DIR/checksums.sig" -out "$TEMP_DIR/checksums.sig.bin"
if ! openssl pkeyutl -verify \
-pubin \
-inkey "$TEMP_DIR/release-signing-public.pem" \
-sigfile "$TEMP_DIR/checksums.sig.bin" \
-rawin \
-in "$TEMP_DIR/checksums.json" >/dev/null 2>&1; then
echo "ERROR: checksums.json signature verification failed" >&2
exit 1
fi
EXPECTED_ZIP_SHA="$(jq -r '.archive.sha256 // empty' "$TEMP_DIR/checksums.json")"
if [ -z "$EXPECTED_ZIP_SHA" ]; then
echo "ERROR: checksums.json missing archive.sha256" >&2
exit 1
fi
if command -v shasum >/dev/null 2>&1; then
ACTUAL_ZIP_SHA="$(shasum -a 256 "$TEMP_DIR/$ZIP_NAME" | awk '{print $1}')"
else
ACTUAL_ZIP_SHA="$(sha256sum "$TEMP_DIR/$ZIP_NAME" | awk '{print $1}')"
fi
if [ "$EXPECTED_ZIP_SHA" != "$ACTUAL_ZIP_SHA" ]; then
echo "ERROR: Archive checksum mismatch for $ZIP_NAME" >&2
exit 1
fi
echo "Checksums manifest signature and archive hash verified."
# 3) 安装已验证的存档
mkdir -p "$INSTALL_ROOT"
rm -rf "$DEST"
unzip -q "$TEMP_DIR/$ZIP_NAME" -d "$INSTALL_ROOT"
chmod 600 "$DEST/skill.json"
find "$DEST" -type f ! -name "skill.json" -exec chmod 644 {} \;
echo "Installed clawsec-suite v${VERSION} to: $DEST"
echo "Next step (OpenClaw): node \"\$DEST/scripts/setup_advisory_hook.mjs\""
安装套件后,启用通告守护钩子:
SUITE_DIR="${INSTALL_ROOT:-$HOME/.openclaw/skills}/clawsec-suite"
node "$SUITE_DIR/scripts/setup_advisory_hook.mjs"
可选:创建/更新一个周期性定时任务提醒(默认每 6h),用于触发主会话的通告扫描:
SUITE_DIR="${INSTALL_ROOT:-$HOME/.openclaw/skills}/clawsec-suite"
node "$SUITE_DIR/scripts/setup_advisory_cron.mjs"
这会添加的功能:
agent:bootstrap 和 /new (command:new) 时进行扫描,affected 条目与已安装技能进行比对,application: "openclaw" 的通告(以及为了向后兼容,没有 application 的旧条目),启用钩子后,重启 OpenClaw 网关。然后运行一次 /new 以在下一个会话上下文中强制立即扫描。
当用户请求安装一个技能时,将其视为第一次请求,并运行受保护的安装检查:
SUITE_DIR="${INSTALL_ROOT:-$HOME/.openclaw/skills}/clawsec-suite"
node "$SUITE_DIR/scripts/guarded_skill_install.mjs" --skill helper-plus --version 1.0.1
行为:
如果未找到匹配的通告,则继续安装。
如果省略 --version,匹配是保守的:任何引用该技能名称的通告都被视为匹配。
如果找到匹配的通告,脚本会打印通告上下文并以代码 42 退出。
然后需要用户明确的第二次确认,并使用 --confirm-advisory 重新运行:
node "$SUITE_DIR/scripts/guarded_skill_install.mjs" --skill helper-plus --version 1.0.1 --confirm-advisory
这强制执行:
嵌入式源逻辑使用以下默认值:
https://clawsec.prompt.security/advisories/feed.json${CLAWSEC_FEED_URL}.sig(可通过 CLAWSEC_FEED_SIG_URL 覆盖)checksums.json(可通过 CLAWSEC_FEED_CHECKSUMS_URL 覆盖)~/.openclaw/skills/clawsec-suite/advisories/feed.json${CLAWSEC_LOCAL_FEED}.sig(可通过 CLAWSEC_LOCAL_FEED_SIG 覆盖)~/.openclaw/skills/clawsec-suite/advisories/checksums.json~/.openclaw/skills/clawsec-suite/advisories/feed-signing-public.pem(可通过 CLAWSEC_FEED_PUBLIC_KEY 覆盖)~/.openclaw/clawsec-suite-feed-state.jsonCLAWSEC_HOOK_INTERVAL_SECONDS(默认 300)故障关闭验证: 默认情况下需要源签名。当配套的校验和工件可用时,会验证校验和清单。仅在采用此版本后、上游签名源工件可用之前的临时迁移期间,才将 CLAWSEC_ALLOW_UNSIGNED_FEED=1 作为临时绕过设置。
FEED_URL="${CLAWSEC_FEED_URL:-https://clawsec.prompt.security/advisories/feed.json}"
STATE_FILE="${CLAWSEC_SUITE_STATE_FILE:-$HOME/.openclaw/clawsec-suite-feed-state.json}"
TMP="$(mktemp -d)"
trap 'rm -rf "$TMP"' EXIT
if ! curl -fsSLo "$TMP/feed.json" "$FEED_URL"; then
echo "ERROR: Failed to fetch advisory feed"
exit 1
fi
if ! jq -e '.version and (.advisories | type == "array")' "$TMP/feed.json" >/dev/null; then
echo "ERROR: Invalid advisory feed format"
exit 1
fi
mkdir -p "$(dirname "$STATE_FILE")"
if [ ! -f "$STATE_FILE" ]; then
echo '{"schema_version":"1.0","known_advisories":[],"last_feed_check":null,"last_feed_updated":null}' > "$STATE_FILE"
chmod 600 "$STATE_FILE"
fi
NEW_IDS_FILE="$TMP/new_ids.txt"
jq -r --argfile state "$STATE_FILE" '($state.known_advisories // []) as $known | [.advisories[]?.id | select(. != null and ($known | index(.) | not))] | .[]?' "$TMP/feed.json" > "$NEW_IDS_FILE"
if [ -s "$NEW_IDS_FILE" ]; then
echo "New advisories detected:"
while IFS= read -r id; do
[ -z "$id" ] && continue
jq -r --arg id "$id" '.advisories[] | select(.id == $id) | "- [\(.severity | ascii_upcase)] \(.id): \(.title)"' "$TMP/feed.json"
jq -r --arg id "$id" '.advisories[] | select(.id == $id) | " Exploitability: \(.exploitability_score // "unknown" | ascii_upcase)"' "$TMP/feed.json"
done < "$NEW_IDS_FILE"
else
echo "FEED_OK - no new advisories"
fi
源中的通告可以包含 exploitability_score 和 exploitability_rationale 字段,以帮助代理优先处理现实世界的威胁:
high、medium、low 或 unknown处理通告时,除了严重性之外,还应按可利用性进行优先级排序。一个 HIGH 严重性 + HIGH 可利用性的 CVE 比一个 CRITICAL 严重性 + LOW 可利用性的 CVE 更紧急。
有关详细方法,请参阅可利用性评分文档。
使用套件心跳脚本作为单一的周期性安全检查入口点:
skills/clawsec-suite/HEARTBEAT.md它处理:
如果一个通告指示存在恶意或建议移除的技能,并且该技能已安装:
套件钩子和心跳指导默认情况下是故意非破坏性的。
通告守护管道支持对已由安全团队审查并接受的通告进行选择性抑制。这对于内部工具或不适用于您部署的通告非常有用。
通告抑制需要一个单一的门控:配置文件必须包含 "enabledFor" 数组,且数组中包含 "advisory"。不需要 CLI 标志——配置文件中的哨兵就是选择性加入的门控。
如果 enabledFor 数组缺失、为空或不包含 "advisory",则所有通告都会正常报告。
通告守护程序使用与审计管道相同的优先级顺序来解析抑制配置:
--config <路径> 参数OPENCLAW_AUDIT_CONFIG 环境变量~/.openclaw/security-audit.json.clawsec/allowlist.json{
"enabledFor": ["advisory"],
"suppressions": [
{
"checkId": "CVE-2026-25593",
"skill": "clawsec-suite",
"reason": "First-party security tooling — reviewed by security team",
"suppressedAt": "2026-02-15"
},
{
"checkId": "CLAW-2026-0001",
"skill": "example-skill",
"reason": "Advisory does not apply to our deployment configuration",
"suppressedAt": "2026-02-16"
}
]
}
"enabledFor": ["advisory"] —— 仅激活通告抑制"enabledFor": ["audit"] —— 仅激活审计抑制(对通告管道无影响)"enabledFor": ["audit", "advisory"] —— 两个管道都遵守抑制规则enabledFor —— 无抑制激活(安全默认值)CVE-2026-25593 或 CLAW-2026-0001)| 字段 | 描述 | 示例 |
|---|---|---|
checkId | 要抑制的通告 ID | CVE-2026-25593 |
skill | 受影响的技能名称 | clawsec-suite |
reason | 审计追踪的理由(必需) | First-party tooling, reviewed by security team |
suppressedAt | ISO 8601 日期(YYYY-MM-DD) | 2026-02-15 |
通告和审计管道共享同一个配置文件。使用 enabledFor 数组来控制哪些管道遵守抑制列表:
{
"enabledFor": ["audit", "advisory"],
"suppressions": [
{
"checkId": "skills.code_safety",
"skill": "clawsec-suite",
"reason": "First-party tooling — audit finding accepted",
"suppressedAt": "2026-02-15"
},
{
"checkId": "CVE-2026-25593",
"skill": "clawsec-suite",
"reason": "First-party tooling — advisory reviewed",
"suppressedAt": "2026-02-15"
}
]
}
审计条目(带有如 skills.code_safety 这样的检查标识符)仅由审计管道匹配。通告条目(带有如 CVE-2026-25593 或 CLAW-2026-0001 这样的通告 ID)仅由通告管道匹配。每个管道都过滤其自身相关的条目。
动态发现当前可安装的技能,然后安装您想要的技能:
SUITE_DIR="${INSTALL_ROOT:-$HOME/.openclaw/skills}/clawsec-suite"
node "$SUITE_DIR/scripts/discover_skill_catalog.mjs"
# 然后按名称安装任何发现的技能
npx clawhub@latest install <skill-name>
也可用于自动化的机器可读输出:
node "$SUITE_DIR/scripts/discover_skill_catalog.mjs" --json
checksums.json 的签名,然后验证每个文件的校验和。CLAWSEC_ALLOW_UNSIGNED_FEED。critical 和 high 通告视为需要立即处理的事项。clawsec-feed 迁移,请保留一个规范的状态文件,以避免重复通知。每周安装量
445
仓库
GitHub 星标数
830
首次出现
2026年2月10日
安全审计
安装于
opencode427
codex425
gemini-cli424
cursor424
kimi-cli419
github-copilot418
This means clawsec-suite can:
advisories/feed.jsonHEARTBEAT.mdhooks/clawsec-advisory-guardian/scripts/scripts/guarded_skill_install.mjsscripts/discover_skill_catalog.mjsclawsec-suite does not hard-code add-on skill names in this document.
Discover the current catalog from the authoritative index (https://clawsec.prompt.security/skills/index.json) at runtime:
SUITE_DIR="${INSTALL_ROOT:-$HOME/.openclaw/skills}/clawsec-suite"
node "$SUITE_DIR/scripts/discover_skill_catalog.mjs"
Fallback behavior:
skill.json.bash/zsh, keep path variables expandable (for example, INSTALL_ROOT="$HOME/.openclaw/skills").'$HOME/.openclaw/skills').$env:INSTALL_ROOT = Join-Path $HOME ".openclaw\\skills"\$HOME/...), suite scripts now fail fast with a clear error.npx clawhub@latest install clawsec-suite
set -euo pipefail
VERSION="${SKILL_VERSION:?Set SKILL_VERSION (e.g. 0.0.8)}"
INSTALL_ROOT="${INSTALL_ROOT:-$HOME/.openclaw/skills}"
DEST="$INSTALL_ROOT/clawsec-suite"
BASE="https://github.com/prompt-security/clawsec/releases/download/clawsec-suite-v${VERSION}"
TEMP_DIR="$(mktemp -d)"
trap 'rm -rf "$TEMP_DIR"' EXIT
# Pinned release-signing public key (verify fingerprint out-of-band on first use)
# Fingerprint (SHA-256 of SPKI DER): 711424e4535f84093fefb024cd1ca4ec87439e53907b305b79a631d5befba9c8
RELEASE_PUBKEY_SHA256="711424e4535f84093fefb024cd1ca4ec87439e53907b305b79a631d5befba9c8"
cat > "$TEMP_DIR/release-signing-public.pem" <<'PEM'
-----BEGIN PUBLIC KEY-----
MCowBQYDK2VwAyEAS7nijfMcUoOBCj4yOXJX+GYGv2pFl2Yaha1P4v5Cm6A=
-----END PUBLIC KEY-----
PEM
ACTUAL_KEY_SHA256="$(openssl pkey -pubin -in "$TEMP_DIR/release-signing-public.pem" -outform DER | shasum -a 256 | awk '{print $1}')"
if [ "$ACTUAL_KEY_SHA256" != "$RELEASE_PUBKEY_SHA256" ]; then
echo "ERROR: Release public key fingerprint mismatch" >&2
exit 1
fi
ZIP_NAME="clawsec-suite-v${VERSION}.zip"
# 1) Download release archive + signed checksums manifest + signing public key
curl -fsSL "$BASE/$ZIP_NAME" -o "$TEMP_DIR/$ZIP_NAME"
curl -fsSL "$BASE/checksums.json" -o "$TEMP_DIR/checksums.json"
curl -fsSL "$BASE/checksums.sig" -o "$TEMP_DIR/checksums.sig"
# 2) Verify checksums manifest signature before trusting any hashes
openssl base64 -d -A -in "$TEMP_DIR/checksums.sig" -out "$TEMP_DIR/checksums.sig.bin"
if ! openssl pkeyutl -verify \
-pubin \
-inkey "$TEMP_DIR/release-signing-public.pem" \
-sigfile "$TEMP_DIR/checksums.sig.bin" \
-rawin \
-in "$TEMP_DIR/checksums.json" >/dev/null 2>&1; then
echo "ERROR: checksums.json signature verification failed" >&2
exit 1
fi
EXPECTED_ZIP_SHA="$(jq -r '.archive.sha256 // empty' "$TEMP_DIR/checksums.json")"
if [ -z "$EXPECTED_ZIP_SHA" ]; then
echo "ERROR: checksums.json missing archive.sha256" >&2
exit 1
fi
if command -v shasum >/dev/null 2>&1; then
ACTUAL_ZIP_SHA="$(shasum -a 256 "$TEMP_DIR/$ZIP_NAME" | awk '{print $1}')"
else
ACTUAL_ZIP_SHA="$(sha256sum "$TEMP_DIR/$ZIP_NAME" | awk '{print $1}')"
fi
if [ "$EXPECTED_ZIP_SHA" != "$ACTUAL_ZIP_SHA" ]; then
echo "ERROR: Archive checksum mismatch for $ZIP_NAME" >&2
exit 1
fi
echo "Checksums manifest signature and archive hash verified."
# 3) Install verified archive
mkdir -p "$INSTALL_ROOT"
rm -rf "$DEST"
unzip -q "$TEMP_DIR/$ZIP_NAME" -d "$INSTALL_ROOT"
chmod 600 "$DEST/skill.json"
find "$DEST" -type f ! -name "skill.json" -exec chmod 644 {} \;
echo "Installed clawsec-suite v${VERSION} to: $DEST"
echo "Next step (OpenClaw): node \"\$DEST/scripts/setup_advisory_hook.mjs\""
After installing the suite, enable the advisory guardian hook:
SUITE_DIR="${INSTALL_ROOT:-$HOME/.openclaw/skills}/clawsec-suite"
node "$SUITE_DIR/scripts/setup_advisory_hook.mjs"
Optional: create/update a periodic cron nudge (default every 6h) that triggers a main-session advisory scan:
SUITE_DIR="${INSTALL_ROOT:-$HOME/.openclaw/skills}/clawsec-suite"
node "$SUITE_DIR/scripts/setup_advisory_cron.mjs"
What this adds:
agent:bootstrap and /new (command:new),affected entries against installed skills,application: "openclaw" (and legacy entries without application for backward compatibility),Restart the OpenClaw gateway after enabling the hook. Then run /new once to force an immediate scan in the next session context.
When the user asks to install a skill, treat that as the first request and run a guarded install check:
SUITE_DIR="${INSTALL_ROOT:-$HOME/.openclaw/skills}/clawsec-suite"
node "$SUITE_DIR/scripts/guarded_skill_install.mjs" --skill helper-plus --version 1.0.1
Behavior:
If no advisory match is found, install proceeds.
If --version is omitted, matching is conservative: any advisory that references the skill name is treated as a match.
If advisory match is found, the script prints advisory context and exits with code 42.
Then require an explicit second confirmation from the user and rerun with --confirm-advisory:
node "$SUITE_DIR/scripts/guarded_skill_install.mjs" --skill helper-plus --version 1.0.1 --confirm-advisory
This enforces:
The embedded feed logic uses these defaults:
https://clawsec.prompt.security/advisories/feed.json${CLAWSEC_FEED_URL}.sig (override with CLAWSEC_FEED_SIG_URL)checksums.json (override with CLAWSEC_FEED_CHECKSUMS_URL)~/.openclaw/skills/clawsec-suite/advisories/feed.json${CLAWSEC_LOCAL_FEED}.sig (override with CLAWSEC_LOCAL_FEED_SIG)~/.openclaw/skills/clawsec-suite/advisories/checksums.jsonFail-closed verification: Feed signatures are required by default. Checksum manifests are verified when companion checksum artifacts are available. Set CLAWSEC_ALLOW_UNSIGNED_FEED=1 only as a temporary migration bypass when adopting this version before signed feed artifacts are available upstream.
FEED_URL="${CLAWSEC_FEED_URL:-https://clawsec.prompt.security/advisories/feed.json}"
STATE_FILE="${CLAWSEC_SUITE_STATE_FILE:-$HOME/.openclaw/clawsec-suite-feed-state.json}"
TMP="$(mktemp -d)"
trap 'rm -rf "$TMP"' EXIT
if ! curl -fsSLo "$TMP/feed.json" "$FEED_URL"; then
echo "ERROR: Failed to fetch advisory feed"
exit 1
fi
if ! jq -e '.version and (.advisories | type == "array")' "$TMP/feed.json" >/dev/null; then
echo "ERROR: Invalid advisory feed format"
exit 1
fi
mkdir -p "$(dirname "$STATE_FILE")"
if [ ! -f "$STATE_FILE" ]; then
echo '{"schema_version":"1.0","known_advisories":[],"last_feed_check":null,"last_feed_updated":null}' > "$STATE_FILE"
chmod 600 "$STATE_FILE"
fi
NEW_IDS_FILE="$TMP/new_ids.txt"
jq -r --argfile state "$STATE_FILE" '($state.known_advisories // []) as $known | [.advisories[]?.id | select(. != null and ($known | index(.) | not))] | .[]?' "$TMP/feed.json" > "$NEW_IDS_FILE"
if [ -s "$NEW_IDS_FILE" ]; then
echo "New advisories detected:"
while IFS= read -r id; do
[ -z "$id" ] && continue
jq -r --arg id "$id" '.advisories[] | select(.id == $id) | "- [\(.severity | ascii_upcase)] \(.id): \(.title)"' "$TMP/feed.json"
jq -r --arg id "$id" '.advisories[] | select(.id == $id) | " Exploitability: \(.exploitability_score // "unknown" | ascii_upcase)"' "$TMP/feed.json"
done < "$NEW_IDS_FILE"
else
echo "FEED_OK - no new advisories"
fi
Advisories in the feed can include exploitability_score and exploitability_rationale fields to help agents prioritize real-world threats:
high, medium, low, or unknownWhen processing advisories, prioritize by exploitability in addition to severity. A HIGH severity + HIGH exploitability CVE is more urgent than a CRITICAL severity + LOW exploitability CVE.
For detailed methodology, see the exploitability scoring documentation.
Use the suite heartbeat script as the single periodic security check entrypoint:
skills/clawsec-suite/HEARTBEAT.mdIt handles:
If an advisory indicates a malicious or removal-recommended skill and that skill is installed:
The suite hook and heartbeat guidance are intentionally non-destructive by default.
The advisory guardian pipeline supports opt-in suppression for advisories that have been reviewed and accepted by your security team. This is useful for first-party tooling or advisories that do not apply to your deployment.
Advisory suppression requires a single gate: the configuration file must contain "enabledFor" with "advisory" in the array. No CLI flag is needed -- the sentinel in the config file IS the opt-in gate.
If the enabledFor array is missing, empty, or does not include "advisory", all advisories are reported normally.
The advisory guardian resolves the suppression config using the same priority order as the audit pipeline:
--config <path> argumentOPENCLAW_AUDIT_CONFIG environment variable~/.openclaw/security-audit.json.clawsec/allowlist.json{
"enabledFor": ["advisory"],
"suppressions": [
{
"checkId": "CVE-2026-25593",
"skill": "clawsec-suite",
"reason": "First-party security tooling — reviewed by security team",
"suppressedAt": "2026-02-15"
},
{
"checkId": "CLAW-2026-0001",
"skill": "example-skill",
"reason": "Advisory does not apply to our deployment configuration",
"suppressedAt": "2026-02-16"
}
]
}
"enabledFor": ["advisory"] -- only advisory suppression active"enabledFor": ["audit"] -- only audit suppression active (no effect on advisory pipeline)"enabledFor": ["audit", "advisory"] -- both pipelines honor suppressionsenabledFor -- no suppression active (safe default)CVE-2026-25593 or CLAW-2026-0001)| Field | Description | Example |
|---|---|---|
checkId | Advisory ID to suppress | CVE-2026-25593 |
skill | Affected skill name | clawsec-suite |
reason | Justification for audit trail (required) | First-party tooling, reviewed by security team |
suppressedAt |
The advisory and audit pipelines share the same config file. Use the enabledFor array to control which pipelines honor the suppression list:
{
"enabledFor": ["audit", "advisory"],
"suppressions": [
{
"checkId": "skills.code_safety",
"skill": "clawsec-suite",
"reason": "First-party tooling — audit finding accepted",
"suppressedAt": "2026-02-15"
},
{
"checkId": "CVE-2026-25593",
"skill": "clawsec-suite",
"reason": "First-party tooling — advisory reviewed",
"suppressedAt": "2026-02-15"
}
]
}
Audit entries (with check identifiers like skills.code_safety) are only matched by the audit pipeline. Advisory entries (with advisory IDs like CVE-2026-25593 or CLAW-2026-0001) are only matched by the advisory pipeline. Each pipeline filters for its own relevant entries.
Discover currently available installable skills dynamically, then install the ones you want:
SUITE_DIR="${INSTALL_ROOT:-$HOME/.openclaw/skills}/clawsec-suite"
node "$SUITE_DIR/scripts/discover_skill_catalog.mjs"
# then install any discovered skill by name
npx clawhub@latest install <skill-name>
Machine-readable output is also available for automation:
node "$SUITE_DIR/scripts/discover_skill_catalog.mjs" --json
checksums.json signature before trusting its file URLs/hashes, then verify each file checksum.CLAWSEC_ALLOW_UNSIGNED_FEED outside temporary migration windows.critical and high advisories affecting installed skills as immediate action items.clawsec-feed, keep one canonical state file to avoid duplicate notifications.Weekly Installs
445
Repository
GitHub Stars
830
First Seen
Feb 10, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
opencode427
codex425
gemini-cli424
cursor424
kimi-cli419
github-copilot418
前端性能优化指南:识别瓶颈与优化策略,提升LCP、FID、CLS核心指标
32,400 周安装
LangChain4j Spring Boot集成指南:AI驱动微服务自动配置与RAG系统实现
349 周安装
Spring Boot Saga模式:微服务分布式事务解决方案与实现指南
349 周安装
WordPress站点设置与连接配置指南:WP-CLI与REST API完整教程
349 周安装
营销心理学实战指南:心智模型与行为设计,提升转化率与用户体验
349 周安装
Spring Boot @JsonTest JSON序列化单元测试指南:JacksonTester使用与最佳实践
349 周安装
scikit-learn 机器学习教程:Python 分类、回归、聚类、降维与模型评估实战指南
350 周安装
~/.openclaw/skills/clawsec-suite/advisories/feed-signing-public.pem (override with CLAWSEC_FEED_PUBLIC_KEY)~/.openclaw/clawsec-suite-feed-state.jsonCLAWSEC_HOOK_INTERVAL_SECONDS (default 300)| ISO 8601 date (YYYY-MM-DD) |
2026-02-15 |