[ralyodio]

Fleet dependency upgrade (2026-10-26). next was already on 16.4.3 here; this takes everything else current.

Security

• bun audit --prod: 14 high -> 0 (1 moderate left: uuid 7/8 inside @telnyx/webrtc)
• bun audit (all): 54 high / 45 moderate -> 10 high / 6 moderate (remaining are dev tooling: picomatch, minimatch 3, brace-expansion 1, fflate)
• serialize-javascript override 7.0.5 -> 7.1.4 (GHSA-m5mm-p8h7-m29v)

Majors taken

@supabase/ssr 0.7 -> 0.12, twilio 5 -> 6, uuid 11 -> 14, dotenv 18, eslint 10, msw 3, mocha 12, sinon 22, sharp 0.35, @vitejs/plugin-react 6, @testing-library/jest-dom 7, @profullstack/stack 0.5 / x402-gateway 0.13 / hqtui 0.11. oven/bun 1.4.0 -> 1.4.4.

src/lib/server/rate-limiter.js exported RateLimiter twice (export class plus a trailing export { RateLimiter }); vite 8's parser rejects that, so the trailing line is gone.

Held

typescript 5.9 (7.x has no JS API), vitest 4, jsdom 26 (jsdom 30 under bun --bun vitest fails every worker on addEventListener).

Gate

vitest 129 files / 841 tests pass (same as master); eslint has 1 error vs 2 on master (the remaining one, a parse error in tests/api/auth/send-sms.test.js, is pre-existing). Booted the real image (docker build + docker run): / 200, container stays up, no errors in logs; /api/health 503 locally only because it points at a fake Supabase. twilio 6 and uuid 14 import and construct under Bun.

🤖 Generated with Claude Code

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	twilio@​5.12.0 ⏵ 6.2.0			+1
	openpgp@​6.2.2 ⏵ 6.3.2			+1	-5
	@​vitest/​ui@​4.1.8 ⏵ 4.1.12				+2
	@​profullstack/​footer@​0.2.5 ⏵ 0.3.0	-1		+1	+1
	vitest@​4.1.8 ⏵ 4.1.12	+1	+2	+1	+2
	@​profullstack/​stack@​0.1.3 ⏵ 0.5.0	+8		+1	+7
	fake-indexeddb@​6.2.5 ⏵ 6.2.6				-4
	posthog-js@​1.381.0 ⏵ 1.438.23			+1	+1
	mlkem@​2.5.0 ⏵ 2.7.0	+1			-3
	react@​19.2.7 ⏵ 19.3.1	+1		+1
	@​noble/​hashes@​2.0.1 ⏵ 2.4.0
	@​noble/​ciphers@​2.0.1 ⏵ 2.4.0				+1
	@​profullstack/​hqtui@​0.10.2 ⏵ 0.11.1	+5		+1	+1
	globals@​14.0.0 ⏵ 17.13.0			+1
	chai@​6.2.2 ⏵ 6.3.0	+1
	@​testing-library/​jest-dom@​6.9.1 ⏵ 7.0.1
	@​supabase/​supabase-js@​2.74.0 ⏵ 2.118.0	-3
	@​profullstack/​x402-gateway@​0.11.0 ⏵ 0.13.1			+1	+1
	uuid@​11.1.0 ⏵ 14.0.3	+1	+2
	@​testing-library/​react@​16.3.2 ⏵ 16.3.3	+1
	ws@​8.18.3 ⏵ 8.22.0		+18
	oxlint@​1.69.0 ⏵ 1.89.0	+1
	zustand@​5.0.14 ⏵ 5.0.16	+1		+1	+6
	react-dom@​19.2.7 ⏵ 19.3.1			+1
	@​vitejs/​plugin-react@​5.2.0 ⏵ 6.1.2	+1
	sinon@​21.0.0 ⏵ 22.1.0			+1	+4
	@​testing-library/​user-event@​14.6.1 ⏵ 14.6.8
	msw@​2.11.3 ⏵ 3.0.3	+5			+2
	libphonenumber-js@​1.12.25 ⏵ 1.13.15	+1
	mocha@​11.7.5 ⏵ 12.0.3				+1
	eslint@​9.39.2 ⏵ 10.13.0	+1			+45
See 3 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Priority	Alert  (click "▶" to expand/collapse)	Action
	Low adoption: npm @profullstack/stack Location: Package overview From: package.json → npm/@profullstack/stack@0.5.0 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@profullstack/stack@0.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn

View full report

[github-actions]

ThreatCrush Security Scan

17 finding(s)

MEDIUM: 13 | LOW: 4

Severity	Rule	Location
MEDIUM	js-unescaped-html-sink	src/app/blog/[slug]/page.jsx:38
MEDIUM	js-unescaped-html-sink	src/app/blog/[slug]/page.jsx:66
MEDIUM	js-unescaped-html-sink	src/app/faq/page.jsx:57
MEDIUM	js-unescaped-html-sink	src/app/layout.jsx:142
MEDIUM	js-unescaped-html-sink	src/app/layout.jsx:146
MEDIUM	js-unescaped-html-sink	src/app/page.jsx:50
MEDIUM	js-open-redirect	src/app/phone/page.jsx:70
MEDIUM	redos-nested-quantifier	src/lib/auth/dns-name.js:88
MEDIUM	redos-nested-quantifier	src/lib/chat/voice-mode.js:116
MEDIUM	redos-nested-quantifier	src/lib/chat/voice-mode.js:121
MEDIUM	js-unescaped-html-sink	src/lib/components/chat/MessageItem.jsx:85
MEDIUM	js-unescaped-html-sink	src/lib/components/chat/MessageItem.jsx:130
MEDIUM	js-unescaped-html-sink	src/lib/components/PitFooter.jsx:15
LOW	secret-generic-credential	src/app/api/auth/register-anon/route.test.js:32
LOW	secret-jwt	tests/debug-sms.js:10
LOW	secret-generic-credential	tests/private-key-import-export.test.js:252
LOW	secret-generic-credential	tests/private-key-import-export.test.js:264

Snippets are redacted; ThreatCrush never prints matched credential material.