Skip to content

chore(deps): resolve Dependabot security advisories (363 → 1) - #3

Merged
clawnchdev merged 1 commit into
masterfrom
chore/dependabot-security-bumps
Jul 21, 2026
Merged

chore(deps): resolve Dependabot security advisories (363 → 1)#3
clawnchdev merged 1 commit into
masterfrom
chore/dependabot-security-bumps

Conversation

@clawnchdev

Copy link
Copy Markdown
Owner

Summary

Clears the Dependabot alert digest for this repo. Local audit (pnpm 9): 363 vulnerabilities (7 critical) → 1 (1 low, no upstream fix).

What changed (package.json + pnpm-lock.yaml only)

Primary fix — bump openclaw 2026.3.282026.6.5. ~271 of the flagged advisories were transitive deps reached through openclaw's tree (.>openclaw>@mariozechner/pi-*>@google/genai>@modelcontextprotocol/sdk>express>…). The newer release carries updated sub-deps and prunes the tree (hence the large lockfile shrink). Not a prerelease (2026.7.x is; skipped it).

In-range refresh via pnpm update — viem, tsdown, tsx, typescript, @types/node, vite → 8.1.5 (clears the 8.0.5 security floor), @noble/hashes, @scure/bip39, @sinclair/typebox, @clawnch/* SDKs.

pnpm.overrides pin the remaining flagged transitive leaves to patched versions tree-wide (their parents pin them below the fix):
tar 7.5.16 (clears the 1 critical) · ws 8.20.1 · js-yaml 4.1.2 · immutable 4.3.9 · brace-expansion 2.1.2 · follow-redirects 1.15.12 · undici (6.23 + 8.5 lines) · cookie 0.7 · tmp 0.2.4 · adm-zip 0.6 · serialize-javascript 7.0.5 · uuid 11.1.1 · @hono/node-server 2.0.5.

Overrides live in package.json pnpm.overrides (this repo targets pnpm 9 — lockfile v9.0). If you move to pnpm ≥10.16, they relocate to pnpm-workspace.yaml.

Verification

  • tsc --noEmit: clean
  • pnpm build: passes (both build steps)
  • pnpm test: 1546 passed / 31 skipped — parity with master

Not fixed (documented)

  • elliptic (1 low) — transitive via ethers > @uniswap/v4-sdk (in @clawnch/clawncher-sdk). No published fix — npm latest is 6.6.1; the advisory's patched 6.6.2 doesn't exist yet. Nothing to upgrade to.

Notes for reviewer

  • vitest held at 4.1.2 (the version resolved on master). 4.1.10 changed test scheduling and increased flakiness of a pre-existing racy testtests/v4-user-tools.test.ts ("enables and disables tools") leaks shared state across tests and flakes on clean master too (verified: master fails it intermittently with zero of my changes). Out of scope here; worth a separate test-isolation fix (the service consults a shared singleton in getEnabledTools()).
  • Commit is SSH-signed (verified).

Clears the Dependabot alert digest for this repo. Audit (pnpm 9):
363 vulnerabilities (7 critical) -> 1 (1 low, no upstream fix).

Primary fix: bump openclaw 2026.3.28 -> 2026.6.5. ~271 of the flagged
advisories were transitive deps reached through openclaw's tree; the
newer release carries updated sub-deps. Typecheck + build pass on the
bump.

Direct/dev deps refreshed within range via pnpm update (viem, tsdown,
tsx, typescript, @types/node, vite 8.1.5, @noble/hashes, @scure/bip39,
@sinclair/typebox, @clawnch/*). vite reaches the 8.0.5 security floor.

pnpm.overrides pin the remaining flagged transitive leaves to patched
versions (tree-wide, since parents pin them below the fix): tar 7.5.16,
ws 8.20.1, js-yaml 4.1.2, immutable 4.3.9, brace-expansion 2.1.2,
follow-redirects 1.15.12, undici (6.23 / 8.5 lines), cookie 0.7,
tmp 0.2.4, adm-zip 0.6, serialize-javascript 7.0.5, uuid 11.1.1,
@hono/node-server 2.0.5.

Held vitest at 4.1.2 (the version resolved on master) — 4.1.10 changed
test scheduling and increased flakiness of a pre-existing racy test
(tests/v4-user-tools.test.ts, shared-state leak; flakes on clean master
too). Not touched here; unrelated to these deps.

Remaining: elliptic (1 low, GHSA transitive via ethers>@uniswap/v4-sdk)
has no published fix — latest is 6.6.1. Nothing to upgrade to yet.
@clawnchdev
clawnchdev merged commit 813d9ad into master Jul 21, 2026
1 of 2 checks passed
@clawnchdev
clawnchdev deleted the chore/dependabot-security-bumps branch July 21, 2026 22:37
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.

1 participant