Pin workflow actions to commit SHAs and npm exactly in publish
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 72/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, typescript
调研方向
Start with .github/workflows/publish.yml and compare its uses: references and npm install command with the suggested changes; then inspect release.yml, drift-check.yml, ci.yml, pages.yml, stale.yml, and label-sync.yml for the remaining action references. Pin actions to full commit SHAs, select an exact npm version, and apply the listed publish workflow changes. Done when the requested workflow hardening is reflected in those files.
由索引模型根据 Issue 内容生成。
描述
Summary
Every workflow uses: points at a mutable tag, including in the publish job that holds id-token: write for npm trusted publishing. publish.yml also installs a floating npm version. This is hardening; there is no known exploit.
Where
.github/workflows/publish.yml:8-10,.github/workflows/publish.yml:19-27(actions/checkout@v7andactions/setup-node@v7underid-token: write;npm install -g npm@^11.5.1;cache: npm).github/workflows/release.yml(contents: write,actions: write).github/workflows/drift-check.yml:18(a third-party org action@v1.20)- every other
uses:in ci.yml, pages.yml, stale.yml and label-sync.yml
Suggested fix
- Pin actions to full commit SHAs with a
# vX.Ycomment, at least in publish.yml and release.yml. Dependabot already watches github-actions and will bump the SHAs. - Pin npm to an exact version in publish.yml.
- Drop
cache: npmfrom the publish job, so a poisoned cache cannot reach the token-minting job. - Consider
npm ci --ignore-scriptsbefore the build in publish.
Getting started
- Relevant files:
.github/workflows/*.yml
Filed by repo-audit/full-audit at e836036. Severity: low. Effort: S. audit-key: dependencies|.github/workflows/publish.yml|uses
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 6
- 平均合并
- 1 天 21 小时
- 30 天内合并 PR
- 8
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
TMHSDigital/godot-correctness-mcp 的其他 Issue
-
enhancement good first issue severity: medium
难度 2/5 1-3 小时 新手友好度 85/100
TMHSDigital/godot-correctness-mcp#123 ·
维护者通常 2 天内回复
-
dependencies good first issue severity: low
难度 2/5 1-3 小时 新手友好度 82/100
TMHSDigital/godot-correctness-mcp#116 ·
维护者通常 2 天内回复
-
bug good first issue severity: low
难度 2/5 1-3 小时 新手友好度 88/100
TMHSDigital/godot-correctness-mcp#107 ·
维护者通常 2 天内回复
-
bug good first issue severity: low
难度 2/5 1-3 小时 新手友好度 85/100
TMHSDigital/godot-correctness-mcp#106 ·
维护者通常 2 天内回复
-
bug good first issue severity: medium
难度 2/5 1-3 小时 新手友好度 84/100
TMHSDigital/godot-correctness-mcp#105 ·
维护者通常 2 天内回复
查看 TMHSDigital/godot-correctness-mcp 的全部 Issue
相似的 Issue
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
难度 2/5 1-3 小时 新手友好度 76/100
openclaw/openclaw#203385 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
nwverse/persona#12800 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 80/100
维护者通常 1 天内回复
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)未关闭
难度 2/5 1-3 小时 新手友好度 62/100
microsoft/playwright#44289 ·
维护者通常 1 天内回复
-
good first issue
难度 2/5 半天 新手友好度 65/100
维护者通常 1 天内回复