Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
igorwarzocha avatar

Security Nextjs

  • 308 installs
  • 125 repo stars
  • Updated February 4, 2026
  • igorwarzocha/opencode-workflows

security-nextjs is a security agent skill that audits and hardens Next.js applications for common vulnerabilities including authentication, headers, SSR data leaks, environment secrets, and route exposure before producti

About

security-nextjs is an opencode-workflows skill for developers shipping Next.js applications who need a structured pre-launch security review. The skill focuses on App Router and Pages Router risks such as misconfigured auth boundaries, missing security headers, accidental SSR data leaks to the client, exposed environment variables, and unintended public API or server action routes. Agents using the skill walk repositories for Next.js-specific patterns—middleware, `getServerSideProps`, server components, and API routes—and produce remediation guidance aligned with production launch gates. Developers invoke it when a Next.js app is feature-complete but not yet hardened for public traffic or compliance review. It complements generic OWASP checklists by anchoring checks to Next.js file conventions, edge middleware, and deployment environments like Vercel or Node hosting.

  • Next.js-specific threat coverage
  • Auth and SSR leak checks
  • Security header guidance
  • Pre-launch hardening workflow
  • OpenCode security automation

Security Nextjs by the numbers

  • 308 all-time installs (skills.sh)
  • +12 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #629 of 2,203 Security skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/igorwarzocha/opencode-workflows --skill security-nextjs

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs308
repo stars125
Last updatedFebruary 4, 2026
Repositoryigorwarzocha/opencode-workflows

How do you audit Next.js apps for production security?

Audit and harden Next.js apps for common vulnerabilities—auth, headers, SSR data leaks, env secrets, and route exposure—before production launch.

Who is it for?

Next.js teams preparing a production launch who need an App Router–aware security pass beyond generic lint rules.

Skip if: Non-Next.js frameworks, pure infrastructure pentests, or apps still in early scaffolding without routes to review.

When should I use this skill?

A Next.js application is nearing launch and needs review of auth, headers, SSR data handling, secrets, and route exposure.

What you get

Security findings list, hardened middleware and headers config, env secret remediation, and route exposure report.

  • security findings report
  • remediation checklist

Files

SKILL.mdMarkdownGitHub ↗

<overview>

Security audit patterns for Next.js applications covering environment variable exposure, Server Actions, middleware auth, API routes, and App Router security.

</overview>

<rules>

Environment Variable Exposure

The NEXT_PUBLIC_ Footgun

NEXT_PUBLIC_* → Bundled into client JavaScript → Visible to everyone
No prefix     → Server-only → Safe for secrets

Audit steps: 1. grep -r "NEXT_PUBLIC_" . -g "*.env*" 2. For each var, ask: "Would I be OK if this was in view-source?" 3. Common mistakes:

  • NEXT_PUBLIC_API_KEY (SHOULD be server-only)
  • NEXT_PUBLIC_DATABASE_URL (MUST NOT use)
  • NEXT_PUBLIC_STRIPE_SECRET_KEY (use STRIPE_SECRET_KEY)

Safe pattern:

// Server-only (API route, Server Component, Server Action)
const apiKey = process.env.API_KEY; // ✓ No NEXT_PUBLIC_

// Client-safe (truly public)
const publishableKey = process.env.NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY; // ✓ Publishable

next.config.js env Is Always Bundled

Values set in next.config.js under env are inlined into the client bundle, even without NEXT_PUBLIC_. Treat them as public.

// ❌ Sensitive values here are exposed to the browser
module.exports = {
  env: {
    DATABASE_URL: process.env.DATABASE_URL,
  },
};

</rules>

<vulnerabilities>

Server Actions Security

Missing Auth (Most Common Issue)

// ❌ VULNERABLE: No auth check
"use server"
export async function deleteUser(userId: string) {
  await db.user.delete({ where: { id: userId } });
}

// ✓ SECURE: Auth + authorization
"use server"
export async function deleteUser(userId: string) {
  const session = await getServerSession();
  if (!session) throw new Error("Unauthorized");
  if (session.user.id !== userId && !session.user.isAdmin) {
    throw new Error("Forbidden");
  }
  await db.user.delete({ where: { id: userId } });
}

Input Validation

// ❌ Trusts client input
"use server"
export async function updateProfile(data: any) {
  await db.user.update({ data });
}

// ✓ Validates with Zod
"use server"
import { z } from "zod";
const schema = z.object({ name: z.string().max(100), bio: z.string().max(500) });
export async function updateProfile(formData: FormData) {
  const data = schema.parse(Object.fromEntries(formData));
  await db.user.update({ data });
}

API Routes Security

App Router (app/api/*/route.ts)

// ❌ No auth
export async function GET(request: Request) {
  return Response.json(await db.users.findMany());
}

// ✓ Auth middleware
import { getServerSession } from "next-auth";
export async function GET(request: Request) {
  const session = await getServerSession();
  if (!session) return new Response("Unauthorized", { status: 401 });
  // ...
}

Pages Router (pages/api/*.ts)

// Check for missing auth on all handlers
// Common issue: GET is public but POST has auth (inconsistent)

Middleware Security

Auth in middleware.ts

// middleware.ts
import { NextResponse } from "next/server";
import type { NextRequest } from "next/server";

export function middleware(request: NextRequest) {
  const token = request.cookies.get("session");
  
  // ❌ Just checking existence
  if (!token) return NextResponse.redirect("/login");
  
  // ✓ SHOULD verify token
  // But middleware can't do async DB calls easily!
  // Solution: Use next-auth middleware or verify JWT
}

// CRITICAL: Check matcher covers all protected routes
export const config = {
  matcher: ["/dashboard/:path*", "/admin/:path*", "/api/admin/:path*"],
};

Matcher Gaps

// ❌ Forgot API routes
matcher: ["/dashboard/:path*"]
// Admin API at /api/admin/* is unprotected!

// ✓ Include API routes
matcher: ["/dashboard/:path*", "/api/admin/:path*"]

Headers & Security Config

next.config.js

// Check for security headers
module.exports = {
  async headers() {
    return [
      {
        source: "/:path*",
        headers: [
          { key: "X-Frame-Options", value: "DENY" },
          { key: "X-Content-Type-Options", value: "nosniff" },
          { key: "Referrer-Policy", value: "strict-origin-when-cross-origin" },
          // CSP is complex - check if present and not too permissive
        ],
      },
    ];
  },
};

</vulnerabilities>

<severity_table>

Common Vulnerabilities

IssueWhere to LookSeverity
NEXT_PUBLIC_ secrets.env* filesCRITICAL
Unauth'd Server Actionsapp/**/actions.tsHIGH
Unauth'd API routesapp/api/**/route.ts, pages/api/**HIGH
Middleware matcher gapsmiddleware.tsHIGH
Missing input validationServer Actions, API routesHIGH
IDOR in dynamic routes[id] params without ownership checkHIGH
dangerouslySetInnerHTMLComponentsMEDIUM
Missing security headersnext.config.jsLOW

</severity_table>

<commands>

Quick Grep Commands

# Find NEXT_PUBLIC_ usage
grep -r "NEXT_PUBLIC_" . -g "*.env*" -g "*.ts" -g "*.tsx"

# Find next.config env usage (always bundled)
rg -n 'env\s*:' next.config.*

# Find Server Actions without auth
rg -l '"use server"' . | xargs rg -L '(getServerSession|auth\(|getSession|currentUser)'

# Find API routes
fd 'route\.(ts|js)' app/api/

# Find dangerouslySetInnerHTML
rg 'dangerouslySetInnerHTML' . -g "*.tsx" -g "*.jsx"

</commands>

Related skills

FAQ

What does security-nextjs check in a Next.js repo?

security-nextjs checks authentication configuration, security headers, SSR and server-component data leaks, environment secret exposure, and unintended public routes. It targets Next.js conventions like middleware, API routes, and server actions before launch.

When should teams run security-nextjs?

Teams should run security-nextjs when a Next.js app is feature-complete and headed to production. It is a pre-launch hardening pass, not a substitute for runtime penetration testing or infrastructure audits.

Securityappsecauditcompliance

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.