Skip to content

chore: allowlist GHSA-ggr8-5vv4-36mx (deepmerge-ts) in audit gate - #19

Open
Vlad G (vladpm) wants to merge 1 commit into
mainfrom
fix/audit-allowlist-deepmerge-ts
Open

chore: allowlist GHSA-ggr8-5vv4-36mx (deepmerge-ts) in audit gate#19
Vlad G (vladpm) wants to merge 1 commit into
mainfrom
fix/audit-allowlist-deepmerge-ts

Conversation

@vladpm

Copy link
Copy Markdown
Contributor

What

Allowlist GHSA-ggr8-5vv4-36mx (deepmerge-ts, transitive via prisma / @prisma/config) in the audit:allowlist gate.

Why

A newly-published high-severity advisory in deepmerge-ts started failing the Audit dependencies CI step on every run — including unrelated PRs such as #18. There is no non-breaking fix: npm audit reports fixAvailable as a semver-major prisma change. The package is reached only when merging developer-authored Prisma config at CLI/build time, not with untrusted runtime input, so the prototype-pollution vector is not exploitable in this app.

Notes

  • No dependency versions change — only the audit allowlist gains one justified entry (mirrors the existing nanoid exception).
  • Remove once prisma ships a patched deepmerge-ts.
  • Validated locally: npm run audit:allowlist exits 0.

A new high-severity advisory in deepmerge-ts (transitive via prisma /
@prisma/config) has no non-breaking fix (npm audit fixAvailable is a
semver-major prisma change). It is reached only when merging
developer-authored Prisma config at CLI/build time, not with untrusted
runtime input, so it is not exploitable in this app. Allowlist with
justification to keep the audit gate meaningful and unblock CI. Remove
once prisma ships a patched deepmerge-ts.
@vladpm Vlad G (vladpm) self-assigned this Aug 28, 2026
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