You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm audit --package-lock-only reported 2 high-severity advisories in this manifest,
confirmed still present on main:
brace-expansion DoS via unbounded expansion length (GHSA-mh99-v99m-4gvg) and a
bypass of that mitigation via unbounded intermediate arrays (GHSA-rgw5-rvv9-x895).
This candidate was flagged as an untried, independent lead in prior release-train
cache-memory notes after several other candidates on github/gh-aw showed a
suspicious non-landing pattern with create_pull_request — this PR also serves as a
fresh data point on whether that pipeline issue has been resolved.
Risk assessment
Runtime/dev/build/CI scope: dev-only — all four vulnerable packages are
transitive devDependencies (via @actions/github-script, archiver-utils, readdir-glob), not shipped in any released artifact.
Direct/transitive: transitive only; no package.json range changes.
Reachability: lockfile-only; no source files in actions/setup/js import brace-expansion or minimatch directly. Not on auth/crypto/payment/db/
serialization/telemetry/CI-runner/container-base surfaces.
Result: audit clean; typecheck passes with no errors.
Remaining gaps: vitest run in this sandbox has ~450 pre-existing failures
unrelated to this change (mock LLM-proxy 429s, a step-summary ENOENT writer
issue, and firewall-network-block assertion drift in update_pr_description_helpers.test.cjs) — confirmed identical failure set with
this commit stashed out, so they predate this bump. Recommend CI's clean
environment for full test confirmation.
Caution
Protected files were modified in this change.
This pull request is in
request-reviewmode and requires explicit human scrutiny before merge.Protected files:
package-lock.jsonDependency Release Train Summary
What changed
actions/setup/js)actions/setup/js/package-lock.json(lockfile-only, nopackage.jsonchange)brace-expansion@1.1.16/2.1.2/5.0.8,minimatch@3.1.2brace-expansion@1.1.18/2.1.4/5.0.9,minimatch@3.1.5npm audit fix --package-lock-only)Why now
npm audit --package-lock-onlyreported 2 high-severity advisories in this manifest,confirmed still present on
main:brace-expansionDoS via unbounded expansion length (GHSA-mh99-v99m-4gvg) and abypass of that mitigation via unbounded intermediate arrays (GHSA-rgw5-rvv9-x895).
minimatchReDoS via repeated wildcards (GHSA-3ppc-4f35-3m26), combinatorialbacktracking via non-adjacent GLOBSTAR segments (GHSA-7r86-cg39-jmmj), and nested
*()extglob backtracking (GHSA-23c5-xmqv-rm74).cache-memory notes after several other candidates on
github/gh-awshowed asuspicious non-landing pattern with
create_pull_request— this PR also serves as afresh data point on whether that pipeline issue has been resolved.
Risk assessment
transitive devDependencies (via
@actions/github-script,archiver-utils,readdir-glob), not shipped in any released artifact.package.jsonrange changes.actions/setup/jsimportbrace-expansionorminimatchdirectly. Not on auth/crypto/payment/db/serialization/telemetry/CI-runner/container-base surfaces.
Validation
npm audit --package-lock-only(before: 2 high, after: 0vulnerabilities),
npm ci --prefer-offline,npx tsc --noEmit(clean).vitest runin this sandbox has ~450 pre-existing failuresunrelated to this change (mock LLM-proxy 429s, a step-summary
ENOENTwriterissue, and firewall-network-block assertion drift in
update_pr_description_helpers.test.cjs) — confirmed identical failure set withthis commit stashed out, so they predate this bump. Recommend CI's clean
environment for full test confirmation.
Sensitive surface area
Breaking-change notes
via
npm audit fix --package-lock-only.Reviewer checklist
Rollback guidance
Control Plane
Smart-Dependabot-Merge-Candidate: yes
Note
This was originally intended as a pull request, but the git push operation failed.
Original error: The process '/usr/bin/git' failed with exit code 128
Workflow Run: View run details and download bundle artifact
The bundle file is available in the
agentartifact in the workflow run linked above.Create the pull request manually
Add this agentic workflow to your repo
To install this agentic workflow, run