nextjs-security-review
Use when a Next.js project or security audit involves App Router, route handlers, middleware, auth, validation, headers, environment variables, deployment, logging, redirects, SSRF, uploads, or rate limits.
- License 许可
- MIT
- 最近更新
- 2026-05-04
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- nextjs-security-review
- metadata
- { "internal": true }
- description
- Use when a Next.js project or security audit involves App Router, route handlers, middleware, auth, validation, headers, environment variables, deployment, logging, redirects, SSRF, uploads, or rate limits.
03 SKILL.md 正文
Next.js Security Review
Required Checks
- App Router conventions and server/client boundaries.
- Route handlers and server actions for input validation.
- Auth and authorization checks on sensitive paths.
- Middleware coverage or documented route-level alternatives.
- Rate limiting on public mutation and AI/model routes.
- Security headers and deployment-layer header evidence.
- Environment validation and client/server secret separation.
- Unsafe redirects, SSRF, file uploads, and raw provider error leakage.
- Logging that may expose headers, cookies, tokens, requests, or model/provider errors.
Evidence
Use concrete files such as middleware.ts, app/api/**/route.ts, next.config.*, env modules, tests, and security docs. If a control is missing, say missing rather than assuming it exists elsewhere.
04 同仓库更多 Skills
dangerous-helper
Unsafe fixture skill for supply-chain audit tests.
benign-helper
Safe fixture skill for supply-chain audit tests.
skill-supply-chain-auditor
Use when reviewing installed skills, adding third-party skills, hardening agent workflows, checking skill correctness, removing duplicate skills, or investigating supply-chain, prompt-injection, secret-leakage, dependency-install, webhook, destructive-shell, manifest-quality, or resource-discovery risks.
refactor-with-tests
Use when splitting files, improving architecture, reducing duplication, changing internals, or preserving behavior through focused tests during refactors.
python-mcp-server-quality
Use when creating, auditing, or improving Python MCP servers, FastMCP tools, resources, prompts, stdio transports, streamable HTTP transports, MCP Inspector setup, or Python tool schemas.
python-backend-quality
Use when reviewing, creating, or improving Python services, CLIs, libraries, FastAPI, Django, Flask, pytest, uv, pyproject, typing, Pydantic, SQLAlchemy, async code, packaging, or deployment.