Skip to content

fix(deps): patch postcss XSS Dependabot alert (#42)#32

Merged
vxcozy merged 1 commit into
mainfrom
claude/postcss-security-patch
May 2, 2026
Merged

fix(deps): patch postcss XSS Dependabot alert (#42)#32
vxcozy merged 1 commit into
mainfrom
claude/postcss-security-patch

Conversation

@vxcozy
Copy link
Copy Markdown
Collaborator

@vxcozy vxcozy commented May 2, 2026

Summary

Resolves Dependabot alert #42postcss < 8.5.10, medium severity (XSS via unescaped </style> in CSS stringify output).

postcss has no direct dependents in this monorepo — it's pulled in transitively by tooling (vite, cssnano, autoprefixer, nuxt, etc.). I added a pnpm override (matching the existing pattern used for vite, @hono/node-server, etc. in package.json) to pin all transitive resolutions to 8.5.10.

Changes

  • package.json: added "postcss@<8.5.10": "8.5.10" to pnpm.overrides.
  • pnpm-lock.yaml: refreshed — every postcss@* reference now resolves to 8.5.10.
  • Patch changeset for the @tomehq/core fixed group.

Test plan

  • pnpm install — clean
  • grep postcss@ pnpm-lock.yaml returns only postcss@8.5.10
  • pnpm exec vitest run packages/api packages/core packages/components — 1463/1463 pass
  • pnpm build — all publishable packages build clean (cli/core/theme/components/editor/create-tome)

🤖 Generated with Claude Code

Adds pnpm override `postcss@<8.5.10` -> `8.5.10`. postcss is purely
transitive (no direct deps), so an override is the cleanest fix. The
lockfile was on 8.5.9, which is vulnerable to XSS via unescaped
</style> in CSS stringify output.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
tome-landing Ignored Ignored May 2, 2026 7:02pm

Request Review

@vxcozy vxcozy merged commit a251026 into main May 2, 2026
11 checks passed
@vxcozy vxcozy deleted the claude/postcss-security-patch branch May 2, 2026 19: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