Skip to content

chore(deps): pin handlebars 4.7.10 via resolutions (fixes Audit on main) - #519

Merged
islandbitcoin merged 1 commit into
mainfrom
jabariennis/chore-handlebars-4-7-10-audit
Oct 11, 2026
Merged

islandbitcoin merged 1 commit into
mainfrom
jabariennis/chore-handlebars-4-7-10-audit

Conversation

@islandbitcoin

Copy link
Copy Markdown
Contributor

Why

The Audit check (make audit = yarn audit --level critical) fails on every PR since the Handlebars 4.7.10 advisories were published (2026-10-05): JavaScript injection via AST type confusion, and via own-property-check bypass. Both are patched in >=4.7.10. Current main pins **/handlebars to 4.7.9.

What

  • package.json resolutions: **/handlebars 4.7.9 → 4.7.10
  • yarn.lock: the single handlebars entry re-resolved to 4.7.10

handlebars is only reached through grpc_tools_node_protoc_ts and spectaql (dev/codegen). No runtime code imports it.

Verification

  • yarn audit --level critical exit code 30 before, 14 after (CI fails at >=16).
  • No other lockfile changes.

Unblocks #518 (ENG-640), whose only failing check is Audit.

🤖 Generated with Claude Code

https://claude.ai/code/session_01G4SaLJF5SWq6sjBEaWJFow

`make audit` (yarn audit --level critical) fails on main since the two
Handlebars advisories published with 4.7.10 (JS injection via AST type
confusion; via own-property-check bypass). handlebars is a transitive dep
of grpc_tools_node_protoc_ts and spectaql only; the existing
`**/handlebars` resolution pinned 4.7.9. Bump it to 4.7.10. No runtime
code path uses handlebars.

Verified: `yarn audit --level critical` exit 14 (no critical) after the
bump, 30 before.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G4SaLJF5SWq6sjBEaWJFow
@islandbitcoin
islandbitcoin merged commit 878e866 into main Oct 11, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants