v0's role in security

I just asked for a security review of my project, below are the top two priority items.

Personally, I would fully expect v0 to be responsible for these items - especially given the audience a product like v0 serves (ie designers and non technical people).

How do you folks see your role in security?

Critical / High Next.js 16.0.10 is badly out of date. pnpm audit lists about 30 advisories against next: Unauthenticated remote code execution (critical): several are in the Image Optimization API. One affects use cache functions, which this app doesn't enable. Other issues: server-side request forgery (SSRF), ways to bypass middleware/proxy checks, denial of service through Server Actions, and cache poisoning. Fix: upgrade to ≥ 16.4.1. While you're there, upgrade react/react-dom from 19.2.0 to the current 19.2.x. Other vulnerable dependencies. These are mostly pulled in by other packages, so updating vanilla-jsoneditor or Scalar, or pinning versions with pnpm.overrides, should clear them: dompurify (many XSS bypasses) sharp/libvips (high) postcss (arbitrary file read) shell-quote (critical) nanoid, lodash, fast-uri, browserslist

Finally, I had two posts to post on this forum, but am restricted to one. That to me is silly.

I just asked for a security review of my project, below are the top two priority items.

Personally, I would fully expect v0 to be responsible for these items - especially given the audience a product like v0 serves (ie designers and non technical people).

How do you folks see your role in security?

Finally, I had two posts to post on this forum, but am restricted to one. That to me is silly.