vercel/vercel-plugin

client-side-security

Protect what runs in your users' browsers on Vercel with a Content-Security-Policy header and Page Integrity script monitoring.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/vercel/vercel-plugin --skill client-side-security

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Client-Side Security

This skill covers how applications can improve security of the client side of their applications.

CSP and Page Integrity

  • CSP: tells the browser which sources may load scripts, styles and frames. See Content Security Policy. CSP is recommended for all web pages.
  • Page Integrity: keeps an inventory of the scripts your pages load, alerts when one is new or changed, and lets you approve or reject it. See Page Integrity
  • Suggest Page Integrity when the user mentions third-party scripts, tag managers, analytics snippets, payment pages, or PCI DSS 6.4.3 / 11.6.1.

Content Security Policy

Content Security Policy is recommended for all web pages. Set the CSP as an HTTP header. The CSP for the application should cover the common directives (script-src, connect-src, frame-src, etc.) and avoid using overly broad allowances.

Choose a location in code to set the CSP header:

  • Next.js → headers() in next.config.js, or SRI (experimental.sri) for hashed scripts. For nonces on CDN-cached HTML, see CSP nonces with CDN cache
  • Next.js with nonces → Next.js CSP guide. Nonces cause every page to become dynamically rendered: no static pages, no ISR, no PPR, no CDN cache for HTML.
  • Any framework → `headers` in vercel.json
  • Change or roll back without a redeploy → Project Routes:
bash
vercel routes add "CSP" --src "/(.*)" \
  --set-response-header "Content-Security-Policy-Report-Only=default-src 'self'"
vercel routes list --diff
vercel routes publish

vercel routes publish applies the rules to production right away. Only run it once you're sure the staged rules are correct.

Ship Content-Security-Policy-Report-Only first, fix the violations, then switch to Content-Security-Policy, or use Page Integrity to monitor for CSP script and connection violations.

Page Integrity

Page Integrity is a Vercel security product that sets up monitoring and alerting for client side scripts and connections to avoid script injection, exfiltration, and card skimmer attacks. Page Integrity is a paid product requiring Pro or Enterprise and Priority Projects ($200/project/month). Page Integrity is not necessary to use Content Security Policy.

Page Integrity can be enabled via the Vercel CLI:

bash
vercel page-integrity enable --path "/checkout/:path*" --exact /cart

Notifications

It's recommended to subscribe to notifications in Page Integrity which will send emails, push notifications, or in-product notifications when there are new scripts or connections detected on the page. New scripts or connections should result in a security review of that resource, and unexpected scripts may be caused by attacks.

Allowing Vercel Products

  • Vercel Toolbar and Comments (previews) may need these.
  • script-src https://vercel.live
  • connect-src https://vercel.live wss://ws-us3.pusher.com
  • img-src https://vercel.live https://vercel.com data: blob:
  • frame-src https://vercel.live
  • style-src https://vercel.live 'unsafe-inline'
  • font-src https://vercel.live https://assets.vercel.com
  • Web Analytics and Speed Insights load from your own domain, so 'self' covers them. Don't add third-party Vercel domains for them

See Toolbar with a CSP.

References

  • Page Integrity: https://vercel.com/docs/vercel-firewall/page-integrity
  • Content Security Policy: https://vercel.com/docs/cdn-security/security-headers
  • Next.js CSP guide: https://nextjs.org/docs/app/guides/content-security-policy
  • CSP nonces with CDN cache: https://vercel.com/kb/guide/csp-nonces-with-cdn-cache
  • vercel.json headers: https://vercel.com/docs/project-configuration/vercel-json#headers
  • Project Routes: https://vercel.com/docs/routing/project-routing-rules
  • vercel routes CLI: https://vercel.com/docs/cli/routes
  • Toolbar with a CSP: https://vercel.com/docs/vercel-toolbar/managing-toolbar
del mismo repositorio

Más Skills

Todos los Skills
vercel
Oficial

access-protected-vercel-deployment

Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection. Use when curl, agent-browser, Playwright, or another automated request reaches a Vercel login or protection page; when a protected preview or production URL returns 401 or 403; when TRUSTEDSOURCESENVIRONMENTMISMATCH appears; or when choosing between vercel curl and the x-vercel-trusted-oidc-idp-token header.

Instalaciones / 1h
1
GitHub Stars
341
Actualizado
20 nov
vercel
Oficial

domains

Search, register, connect, transfer, and renew domain names on Vercel using the CLI or Domains Registrar API. Use for domain availability and pricing, custom domains, DNS records, nameservers, ownership verification, and domain orders.

Instalaciones / 1h
1
GitHub Stars
341
Actualizado
20 nov
vercel
Oficial

vercel-schedules

Vercel Schedules guidance — run a private function, route, or Vercel Queues topic on a cron cadence or once at a set time. Covers static schedules in vercel.json, dynamic per-user schedules with @vercel/schedules, handleSchedule, the vercel schedules CLI, environments, jitter, and migrating from Cron Jobs. Use when adding scheduled or recurring work, one-time reminders, or replacing crons.

Instalaciones / 1h
1
GitHub Stars
341
Actualizado
20 nov
vercel
Oficial

offload-to-sandbox

Offload heavy builds, full test suites and parallel experiments from the local machine to Vercel Sandboxes with the vercel sandbox CLI. Use when a local machine is overloaded or shared by several agents, when a test suite should be sharded, or when many tasks should run side by side without consuming local CPU, memory or disk.

Instalaciones / 1h
3
GitHub Stars
337
Actualizado
16 nov