[sec-check] fix: pin wrangler 4.129.1 via package-lock (deploy-countme-worker.yml / copilot-setup-steps.yml wrangler@latest) - #1075
Open
kubestellar-hive[bot] wants to merge 1 commit into
Open
Conversation
deploy-countme-worker.yml and copilot-setup-steps.yml fetch and execute wrangler@latest from npm at run time in jobs holding CLOUDFLARE_API_TOKEN. This PR adds wrangler 4.129.1 as an exact-pinned devDependency so package-lock.json integrity-pins the tarball. Phase 2 (requires a human with workflows scope — the hive App cannot push workflow edits): change 'npx wrangler@latest deploy' to 'npx wrangler deploy' in deploy-countme-worker.yml, and drop 'npm install -g wrangler@latest' / use 'npx wrangler whoami' in copilot-setup-steps.yml. Refs #1074 Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Security Fix
Cluster claimed:
package.json+package-lock.json(wrangler devDependency pin) in projectbluefin/documentation, for thewrangler@latestsupply-chain exposure in.github/workflows/deploy-countme-worker.yml(CountMe worker deploy) and.github/workflows/copilot-setup-steps.yml(wrangler whoami). No open PR touches these files.Both workflows fetch and execute
wrangler@latestfrom the npm registry at run time, in jobs holding the productionCLOUDFLARE_API_TOKEN/CLOUDFLARE_ACCOUNT_ID. A compromisedwranglerrelease (or install-time dependency) would execute with that token in the environment.This PR (phase 1): adds
wrangler4.129.1as an exact-pinned devDependency sopackage-lock.jsonintegrity-pins the exact tarball. Afternpm ci,npx wranglerresolves to the locked version (verified:npx --no-install wrangler --version→ 4.129.1).Phase 2 — human follow-up required: the hive App lacks
workflowsscope on this repo, so it cannot push edits under.github/workflows/. A maintainer must make these two one-line changes for the fix to take effect:deploy-countme-worker.yml:44:npx wrangler@latest deploy ...→npx wrangler deploy ...copilot-setup-steps.yml: delete thenpm install -g wrangler@lateststep; changewrangler whoami→npx wrangler whoamiRefs #1074
Filed by sec-check agent (ACMM L4/L5 — hold-gated mode). Hold-gated: human review required.
— hive: agent=sec-check backend=copilot model=kimi-k3