chore(main): release together-sandbox-workspace 4.0.4

[github-actions]

🤖 I have created a release beep boop

4.0.4 (2026-08-18)

Bug Fixes

• add snapshot ID filter on list sandboxes (a6d9c05)

---

This PR was generated with Release Please. See documentation.

[broly-code-security-scanner]

Broly Security Scan

Note

Summary

9 actionable finding(s) in this PR
13 total in scan · 4 dismissed false positives

• 🟡 9 medium

5 highest-priority actionable rows in the table below (critical/high first, then top medium).

No finding is at or above high, so this check is not blocking. The findings above are still tracked and reported.

Severity	Scanner	Issue	Location	Dismiss	Verdict
🟡 MEDIUM	SCA	tar@6.2.1 — 11 vulnerabilities (worst: GHSA-23hp-3jrh-7fpw) → >= 7.5.8	package-lock.json:1	d7	🔺 TRUE_POSITIVE · Confidence: HIGH
🟡 MEDIUM	SCA	nanoid@3.3.11 — 2 vulnerabilities (worst: GHSA-28wg-ghj8-5hjv) → >= 3.3.18	package-lock.json:1	d2	🔺 TRUE_POSITIVE · Confidence: HIGH
🟡 MEDIUM	SCA	handlebars@4.7.8 — 7 vulnerabilities (worst: GHSA-2w6w-674q-4c4q) → >= 4.7.9	package-lock.json:1	d5	🔺 TRUE_POSITIVE · Confidence: HIGH
🟡 MEDIUM	SCA	brace-expansion@5.0.4 — 5 vulnerabilities (worst: GHSA-3jxr-9vmj-r5cp) → >= 5.0.8	package-lock.json:1	d4	🔺 TRUE_POSITIVE · Confidence: HIGH
🟡 MEDIUM	SCA	js-yaml@4.1.1 — 3 vulnerabilities (worst: GHSA-52cp-r559-cp3m) → >= 4.3.1	package-lock.json:1	d6	🔺 TRUE_POSITIVE · Confidence: low

🟢 Dismissed false positives (4) — not shown above

• 🟡 MEDIUM · GHSA-67mh-4wv8-2f99: esbuild@0.21.5 · package-lock.json:1 — esbuild@0.21.5 is a transitive dependency of vite/vitest used only for local dev and test running, and is not included in the production runtime image which is built with tsc and ships only runtime dependencies.
• 🟡 MEDIUM · GHSA-g7r4-m6w7-qqqr: esbuild@0.27.7 · package-lock.json:1 — esbuild 0.27.7 is used only through the tsx devDependency for local TypeScript execution, and production runs compiled JavaScript without exposing any esbuild development server.
• 🟡 MEDIUM · vite@5.4.21 — 2 vulnerabilities (worst: GHSA-fx2h-pf6j-xcff) · package-lock.json:1 — vite@5.4.21 is vitest 2's internal dev-only toolchain that never ships to production, where the server is bundled with esbuild and the static client is built by a separate vite 6.4.3.
• 🟡 MEDIUM · GHSA-5xrq-8626-4rwp: vitest@2.1.9 · package-lock.json:1 — vitest is a devDependency test runner that is never shipped in the production runtime image, matching prior org false-positive reasoning confirmed on PR chore: remove legacy core/ runtime and mock directories #17.

Dismiss false positives

Tick a box to dismiss the finding; untick it to bring the finding back. That is the same as replying /broly dismiss d1 and /broly undismiss d1. To record why it is a false positive, reply with /broly dismiss d1: your reason instead — Broly reuses those reasons to triage similar findings across the org.

• d1 · 🟡 MEDIUM   · package-lock.json:1 · GHSA-r5fr-rjxr-66jc: lodash@4.17.23
• d2 · 🟡 MEDIUM   · package-lock.json:1 · nanoid@3.3.11 — 2 vulnerabilities (worst: GHSA-28wg-ghj8-5hjv)
• d3 · 🟡 MEDIUM   · package-lock.json:1 · postcss@8.5.8 — 4 vulnerabilities (worst: GHSA-6g55-p6wh-862q)
• d4 · 🟡 MEDIUM   · package-lock.json:1 · brace-expansion@5.0.4 — 5 vulnerabilities (worst: GHSA-3jxr-9vmj-r5cp)
• d5 · 🟡 MEDIUM   · package-lock.json:1 · handlebars@4.7.8 — 7 vulnerabilities (worst: GHSA-2w6w-674q-4c4q)
• d6 · 🟡 MEDIUM   · package-lock.json:1 · js-yaml@4.1.1 — 3 vulnerabilities (worst: GHSA-52cp-r559-cp3m)
• d7 · 🟡 MEDIUM   · package-lock.json:1 · tar@6.2.1 — 11 vulnerabilities (worst: GHSA-23hp-3jrh-7fpw)
• d8 · 🟡 MEDIUM   · package-lock.json:1 · GHSA-r292-9mhp-454m: tar@7.5.20
• d9 · 🟡 MEDIUM   · package-lock.json:1 · GHSA-hhx9-57xq-r5rw: @hey-api/openapi-ts@0.84.4

Note

Re-scan this PR anytime with /broly scan — useful after /broly undismiss, or to refresh findings without a new push.

Broly — SAST (zai-org/GLM-5.2) · Secrets · SCA · IaC · GH Actions · Base Images · Supply Chain Threats · Exploit Chains · Adversarial Verification

We're continuously improving Broly's accuracy and finding quality — your feedback is valuable. False positives, missed findings, bugs, and feature requests all welcome.