fix(webui,infra): drop private npm registry, httpOnly tokens, Helm secrets, proxy hardening (FC/FH/FM)

[PenguinzTech]

Security fixes (Track A6) — frontend + infra

Targets release/v0.1.x directly (independent of the backend stack — different files).

Critical / high

• FC1 — deleted services/webui/.npmrc (private GitHub Packages registry + NODE_AUTH_TOKEN).
• FC3 — untracked all committed node_modules/ (root, web, services/webui, shared, tests) and gitignored node_modules/, *.tgz, .npmrc.
• FH1 — JWTs no longer in localStorage/zustand-persist; SPA relies on the backend's httpOnly/Secure/SameSite cookies (axios withCredentials); persist stores only non-sensitive user info.
• FH2 — Helm charts support existingSecret; values-prod.yaml references an external secret so prod no longer ships changeme-in-production; inline secretData renders for dev/alpha only.
• FH3 — Express: helmet + CSP + trust proxy + proxyTimeout on both proxies.

Medium

• FM1 — fixed Go-proxy route/baseURL mismatch so /api/go/* reaches the Go backend.
• FM2 — removed NODE_AUTH_TOKEN CI build-arg; added a webui lint/typecheck/build gate before image push.
• FM3 — prod images support @sha256 digest pinning (placeholder + TODO for CI/Renovate).

⚠️ FC2 partial — needs a decision

@penguintechinc/react-libs@1.1.5 is NOT published on public npm (404). The private-registry violation is fully removed, but the package is kept as a vendored file: tarball (which needs no registry/token) as a safe interim so the build still works. To fully close FC2, react-libs 1.1.5 must be published to public npm, then package.json can reference the public version and the tarball can be deleted. Tracked as a TODO in .gitignore and the commit body.

Follow-ups needing network/CI

• services/webui/package-lock.json regenerated for helmet; will be re-validated by the new CI test-webui job on npm ci.
• values-prod.yaml image digests are sha256:PIN_ME placeholders for CI/Renovate to pin.

🤖 Generated with Claude Code

[sourcery-ai]

Sorry, we are unable to review this pull request

The GitHub API does not allow us to fetch diffs exceeding 300 files, and this pull request has 25465

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​helmet@​8.1.0

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Obfuscated code: npm es-abstract is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: services/webui/package-lock.json → npm/eslint-plugin-react@7.37.5 → npm/es-abstract@1.24.2 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es-abstract@1.24.2. 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.
Block		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: services/webui/package-lock.json → npm/puppeteer@24.35.0 → npm/concurrently@9.1.0 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. 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		Low adoption: npm @humanfs/types Location: Package overview From: services/webui/package-lock.json → npm/eslint@9.39.4 → npm/@humanfs/types@0.15.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/@humanfs/types@0.15.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.

View full report