[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DBBTER64RS9XK39HHD8WHH":3,"skill-same:01M7DBBTER64RS9XK39HHD8WHH":56},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7DBBTER64RS9XK39HHD8WHH","supply-chain-security",null,"alicewe1\u002Falice_skill","alicewe1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102134151?v=4","01M7D9STCM8HAESM958JP0989K","Alice_we","01M7D9STDR22MTD9FTTWPAZNV8",64,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fsupply-chain-security\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"﻿---\nx-alice-class: assist\n---\n# Supply Chain Security Testing\n\n> SBOM \u002F SCA \u002F CI\u002FCD 管道 \u002F 依赖溯源\n> 法规驱动：美国行政令 SBOM、中国国标、EU CRA\n\n## 适用场景\n\n- 软件供应链安全评估\n- 开源依赖漏洞扫描与验证\n- CI\u002FCD 管道安全审计\n- 容器镜像安全分析\n- 第三方组件合规审查\n- 构建产物溯源与完整性验证\n\n## 六层供应链治理框架\n\n```text\nLayer 1: 源码信任评估 → 上游仓库\u002F维护者\u002F发布历史审查\nLayer 2: 构建管道集成 → CI\u002FCD 安全门禁、签名验证\nLayer 3: 制品分发完整性 → 签名、校验和、SBOM 附加\nLayer 4: 运行时保护 → 容器扫描、准入控制\nLayer 5: 持续监控 → CVE 实时追踪、漏洞可达性分析\nLayer 6: 事件响应 → 供应链攻击应急、回滚策略\n```\n\n## 工作流\n\n### 1. SBOM 生成与审计\n\n```text\n生成 SBOM：\n□ CycloneDX 格式: cdxgen → bom.json\n□ SPDX 格式: sbom-tool generate\n□ Syft: syft \u003Cimage|dir> -o spdx-json\n\n审计要点：\n□ 是否存在未知\u002F未授权的依赖\n□ 是否存在已废弃\u002F停止维护的包\n□ 许可证冲突检测\n□ 直接依赖 vs 传递依赖清单\n□ 每个组件的发布时间线和维护者状态\n```\n\n### 2. 软件组成分析（SCA）\n\n```bash\n# OSV-Scanner（免费、Google 维护）\nosv-scanner scan -r . --format json\n\n# OWASP Dependency-Track（企业级持续监控）\ndocker run -p 8080:8080 dependencytrack\u002Fapiserver\n# → 上传 SBOM → 自动匹配 NVD\u002FOSV\u002FGitHub Advisory\n\n# Snyk（商业）\nsnyk test --all-projects\nsnyk monitor  # 持续监控\n\n# Trivy（容器 + 依赖 + IaC）\ntrivy fs .          # 文件系统扫描\ntrivy image nginx   # 容器镜像\ntrivy config .      # IaC 配置\n```\n\n### 3. 漏洞可达性验证\n\n```text\nSCA 告警 ≠ 实际风险！大多数 SCA 工具只有 ~15% 的告警是实际可达的。\n\n验证步骤：\n1. 用 Dependency-Track 或 Trivy 获取 CVE 列表\n2. 筛选 CVSS ≥ 7.0 的漏洞\n3. 对有 PoC 的 CVE 做可达性分析\n   - Code Property Graph 切片: 追踪用户输入到漏洞函数的路径\n   - DEPTEX 方法: EPD (Execution Path Dominance) + LLM 语义验证\n4. 在隔离环境中验证 PoC\n5. 对可达的漏洞按实际影响排序修复优先级\n```\n\n工具参考：\n- CodeQL: GitHub 代码查询 → 数据流分析\n- Snyk Code: 可达性标记\n- DEPTEX: LLM 辅助上下文感知风险评估\n\n### 4. CI\u002FCD 管道安全\n\n```text\n安全检查点：\n□ 代码提交 → pre-commit hook: gitleaks (密钥扫描)\n□ PR 阶段 → SCA 扫描 (Trivy\u002FOSV-Scanner)\n□ 构建阶段 → 制品签名 (cosign)\n□ 推送阶段 → SBOM 附加 (syft + attest)\n□ 部署阶段 → 准入控制 (OPA\u002FKyverno + 镜像扫描)\n□ 运行时 → 持续漏洞监控 (Dependency-Track)\n\n管道自身安全：\n□ Pipeline as Code 审计（GitHub Actions \u002F GitLab CI 配置注入）\n□ Runner 隔离（防止恶意构建突破容器）\n□ 密钥管理（Actions Secrets \u002F Vault，禁止硬编码）\n□ 第三方 Action 审查（锁定 commit SHA，非 tag）\n```\n\n### 5. 容器镜像安全\n\n```bash\n# Dockerfile 审计\nhadolint Dockerfile\n\n# 镜像扫描（多层：OS + 应用依赖 + 配置）\ntrivy image --severity HIGH,CRITICAL nginx:latest\n\n# 最小基础镜像\n# 优先: distroless → alpine → slim → 避免 latest\ndocker scout quickview nginx:latest\n\n# 镜像签名\ncosign sign --key cosign.key myimage:tag\ncosign verify --key cosign.pub myimage:tag\n```\n\n### 6. 第三方依赖审查\n\n```text\n新增依赖 Checklist：\n□ 维护状态：最近 6 个月有提交？维护者活跃度？\n□ 安全历史：过去有无被植入恶意代码？\n□ 依赖树：引入后新增多少传递依赖？\n□ 许可证：与项目许可证兼容？\n□ 替代方案：有无更安全的替代（Snyk Advisor \u002F Socket.dev 评分）？\n\n风险评估矩阵：\n  高维护 × 低依赖数 × 兼容许可证 → 低风险\n  低维护 × 高依赖数 × 许可证冲突 → 高风险\n```\n\n## 工具链\n\n| 工具 | 用途 | 获取 |\n|------|------|------|\n| OWASP Dependency-Track | 企业级持续 SCA | `docker pull dependencytrack\u002Fapiserver` |\n| OSV-Scanner | 免费 SCA（OSV.dev 生态） | `go install github.com\u002Fgoogle\u002Fosv-scanner` |\n| Trivy | 镜像 + 依赖 + IaC 扫描 | `apt install trivy` |\n| Syft | SBOM 生成 | `curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fsyft\u002Fmain\u002Finstall.sh` |\n| cdxgen | CycloneDX SBOM 生成 | `npm install -g @cyclonedx\u002Fcdxgen` |\n| Cosign | 容器签名 | `go install github.com\u002Fsigstore\u002Fcosign\u002Fv2\u002Fcmd\u002Fcosign` |\n| Gitleaks | 密钥\u002F凭证扫描 | `go install github.com\u002Fgitleaks\u002Fgitleaks\u002Fv8` |\n| Snyk | 商业 SCA + 可达性 | `npm install -g snyk` |\n| CodeQL | 代码查询 + 数据流 | GitHub Actions 内置 |\n\n## 参考\n\n- `references\u002Fsbom-sca-methodology.md` — SBOM + SCA 方法论\n- `references\u002Fcicd-pipeline-security.md` — CI\u002FCD 管道安全审计\n","# Supply Chain Security Testing\n\n> SBOM \u002F SCA \u002F CI\u002FCD 管道 \u002F 依赖溯源\n> 法规驱动：美国行政令 SBOM、中国国标、EU CRA\n\n## 适用场景\n\n- 软件供应链安全评估\n- 开源依赖漏洞扫描与验证\n- CI\u002FCD 管道安全审计\n- 容器镜像安全分析\n- 第三方组件合规审查\n- 构建产物溯源与完整性验证\n\n## 六层供应链治理框架\n\n```text\nLayer 1: 源码信任评估 → 上游仓库\u002F维护者\u002F发布历史审查\nLayer 2: 构建管道集成 → CI\u002FCD 安全门禁、签名验证\nLayer 3: 制品分发完整性 → 签名、校验和、SBOM 附加\nLayer 4: 运行时保护 → 容器扫描、准入控制\nLayer 5: 持续监控 → CVE 实时追踪、漏洞可达性分析\nLayer 6: 事件响应 → 供应链攻击应急、回滚策略\n```\n\n## 工作流\n\n### 1. SBOM 生成与审计\n\n```text\n生成 SBOM：\n□ CycloneDX 格式: cdxgen → bom.json\n□ SPDX 格式: sbom-tool generate\n□ Syft: syft \u003Cimage|dir> -o spdx-json\n\n审计要点：\n□ 是否存在未知\u002F未授权的依赖\n□ 是否存在已废弃\u002F停止维护的包\n□ 许可证冲突检测\n□ 直接依赖 vs 传递依赖清单\n□ 每个组件的发布时间线和维护者状态\n```\n\n### 2. 软件组成分析（SCA）\n\n```bash\n# OSV-Scanner（免费、Google 维护）\nosv-scanner scan -r . --format json\n\n# OWASP Dependency-Track（企业级持续监控）\ndocker run -p 8080:8080 dependencytrack\u002Fapiserver\n# → 上传 SBOM → 自动匹配 NVD\u002FOSV\u002FGitHub Advisory\n\n# Snyk（商业）\nsnyk test --all-projects\nsnyk monitor  # 持续监控\n\n# Trivy（容器 + 依赖 + IaC）\ntrivy fs .          # 文件系统扫描\ntrivy image nginx   # 容器镜像\ntrivy config .      # IaC 配置\n```\n\n### 3. 漏洞可达性验证\n\n```text\nSCA 告警 ≠ 实际风险！大多数 SCA 工具只有 ~15% 的告警是实际可达的。\n\n验证步骤：\n1. 用 Dependency-Track 或 Trivy 获取 CVE 列表\n2. 筛选 CVSS ≥ 7.0 的漏洞\n3. 对有 PoC 的 CVE 做可达性分析\n   - Code Property Graph 切片: 追踪用户输入到漏洞函数的路径\n   - DEPTEX 方法: EPD (Execution Path Dominance) + LLM 语义验证\n4. 在隔离环境中验证 PoC\n5. 对可达的漏洞按实际影响排序修复优先级\n```\n\n工具参考：\n- CodeQL: GitHub 代码查询 → 数据流分析\n- Snyk Code: 可达性标记\n- DEPTEX: LLM 辅助上下文感知风险评估\n\n### 4. CI\u002FCD 管道安全\n\n```text\n安全检查点：\n□ 代码提交 → pre-commit hook: gitleaks (密钥扫描)\n□ PR 阶段 → SCA 扫描 (Trivy\u002FOSV-Scanner)\n□ 构建阶段 → 制品签名 (cosign)\n□ 推送阶段 → SBOM 附加 (syft + attest)\n□ 部署阶段 → 准入控制 (OPA\u002FKyverno + 镜像扫描)\n□ 运行时 → 持续漏洞监控 (Dependency-Track)\n\n管道自身安全：\n□ Pipeline as Code 审计（GitHub Actions \u002F GitLab CI 配置注入）\n□ Runner 隔离（防止恶意构建突破容器）\n□ 密钥管理（Actions Secrets \u002F Vault，禁止硬编码）\n□ 第三方 Action 审查（锁定 commit SHA，非 tag）\n```\n\n### 5. 容器镜像安全\n\n```bash\n# Dockerfile 审计\nhadolint Dockerfile\n\n# 镜像扫描（多层：OS + 应用依赖 + 配置）\ntrivy image --severity HIGH,CRITICAL nginx:latest\n\n# 最小基础镜像\n# 优先: distroless → alpine → slim → 避免 latest\ndocker scout quickview nginx:latest\n\n# 镜像签名\ncosign sign --key cosign.key myimage:tag\ncosign verify --key cosign.pub myimage:tag\n```\n\n### 6. 第三方依赖审查\n\n```text\n新增依赖 Checklist：\n□ 维护状态：最近 6 个月有提交？维护者活跃度？\n□ 安全历史：过去有无被植入恶意代码？\n□ 依赖树：引入后新增多少传递依赖？\n□ 许可证：与项目许可证兼容？\n□ 替代方案：有无更安全的替代（Snyk Advisor \u002F Socket.dev 评分）？\n\n风险评估矩阵：\n  高维护 × 低依赖数 × 兼容许可证 → 低风险\n  低维护 × 高依赖数 × 许可证冲突 → 高风险\n```\n\n## 工具链\n\n| 工具 | 用途 | 获取 |\n|------|------|------|\n| OWASP Dependency-Track | 企业级持续 SCA | `docker pull dependencytrack\u002Fapiserver` |\n| OSV-Scanner | 免费 SCA（OSV.dev 生态） | `go install github.com\u002Fgoogle\u002Fosv-scanner` |\n| Trivy | 镜像 + 依赖 + IaC 扫描 | `apt install trivy` |\n| Syft | SBOM 生成 | `curl -sSfL https:\u002F\u002Fraw.githubusercontent.com\u002Fanchore\u002Fsyft\u002Fmain\u002Finstall.sh` |\n| cdxgen | CycloneDX SBOM 生成 | `npm install -g @cyclonedx\u002Fcdxgen` |\n| Cosign | 容器签名 | `go install github.com\u002Fsigstore\u002Fcosign\u002Fv2\u002Fcmd\u002Fcosign` |\n| Gitleaks | 密钥\u002F凭证扫描 | `go install github.com\u002Fgitleaks\u002Fgitleaks\u002Fv8` |\n| Snyk | 商业 SCA + 可达性 | `npm install -g snyk` |\n| CodeQL | 代码查询 + 数据流 | GitHub Actions 内置 |\n\n## 参考\n\n- `references\u002Fsbom-sca-methodology.md` — SBOM + SCA 方法论\n- `references\u002Fcicd-pipeline-security.md` — CI\u002FCD 管道安全审计\n",{"x-alice-class":23},"assist","main","19a54ac988e9929160334271f5c1924ddd9b227e","_modules\u002Fsupply-chain-security",19,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill","https:\u002F\u002Fgithub.com\u002Falicewe1","写一些自己用得上的工具，能自动化就绝不手动 · 自动化 \u002F 工程效率 \u002F Agent 技能生态 · 保持好奇，持续构建","2026-09-30 00:41:20",{"source":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add alicewe1\u002Falice_skill --skill supply-chain-security",{"tool":38,"command":39},"bunx","bunx skills add alicewe1\u002Falice_skill --skill supply-chain-security",{"tool":41,"command":42},"pnpm","pnpm dlx skills add alicewe1\u002Falice_skill --skill supply-chain-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fsupply-chain-security\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fcicd-pipeline-security.md","REFERENCE","参考文档",3489,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fsupply-chain-security\u002Freferences\u002Fcicd-pipeline-security.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fsbom-sca-methodology.md",2046,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fsupply-chain-security\u002Freferences\u002Fsbom-sca-methodology.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M7DBMD9P6R27SWQCW5HYVWG0","alice","Alice 六类技能总路由。用户输入 Alice 或要求查看 Alice 技能菜单时，严格输出固定菜单；输入攻\u002F防模式、六类入口或直接描述任务时，按类别→领域→模块渐进路由。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Faliceskill\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7DBM8X5M7YXPYBVFMWF8HRC","alice-reverse","逆向分析渐进路由（二进制 \u002F 移动端 \u002F 协议 \u002F 取证 \u002F 保护机制 \u002F 运行时观测）。触发词：二进制\u002F移动端\u002F反编译\u002FFrida\u002FIDA\u002FGhidra\u002FPE\u002FELF\u002FAPK\u002F协议\u002F取证；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-reverse\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7DBM630E2YKQP29194TT7HC","alice-pentest","web安全渐进路由（Web \u002F API \u002F 资产发现 \u002F 漏洞验证 \u002F 云与网络安全）。触发词：Web\u002FAPI\u002F资产发现\u002F端口\u002F漏洞验证\u002F云与网络安全；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-pentest\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7DBM20M2VDYV5D3MYDGBTQX","alice-game","游戏攻防渐进路由（游戏客户端 \u002F 内存 \u002F 图形 \u002F 反作弊 \u002F 安全研究）。触发词：游戏客户端\u002F内存\u002F图形\u002F偏移\u002F反作弊\u002F模拟器\u002F覆盖层；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-game\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7DBKXVEKB8931MZG23VACFN","alice-crack","卡密授权渐进路由（卡密 \u002F 激活 \u002F 授权验证 \u002F 许可证管理 \u002F 本地授权分析）。触发词：卡密\u002F激活\u002F授权验证\u002Flicense\u002F机器码\u002F试用状态；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-crack\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7DBKTMT90MGV2WP8K73TMQD","alice-assist","技能指令渐进路由（技能路由 \u002F 评分 \u002F 吸收 \u002F 迁移 \u002F 自动化 \u002F 文档与平台集成）。触发词：技能创建\u002F吸收\u002F评分\u002F迁移\u002F自动化\u002F文档\u002F平台指令；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-assist\u002FSKILL.md",[],[]]