middleware-auth Cursor ruleA
middleware-auth from vibestackdev/vibe-stack is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add vibestackdev/vibe-stack/.cursor/rules/middleware-auth.mdc@git:20260401.d240055Pins git:20260401.d240055 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- vibestackdev/vibe-stack
- Path
.cursor/rules/middleware-auth.mdc- Versions recorded
- 1
- Latest version
- git:20260401.d240055, committed Apr 1, 2026
- Size
- 2,309 bytes
- Repository stars
- 8
- License
- MIT
Next.js middleware auth — prevents auth logic being placed in middleware instead of route handlers.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Middleware Auth Rules
## RULE 1: Middleware is for Session REFRESH, Not Auth Enforcement
SECURITY CRITICAL: Next.js middleware CANNOT securely enforce authentication.
Middleware runs on the Edge Runtime and cannot verify Supabase JWTs reliably.
The ONLY job of middleware is to call `updateSession()` to refresh the token.
✅ CORRECT — middleware only refreshes:
```typescript
// middleware.ts
import { updateSession } from '@/lib/supabase/middleware'
import { type NextRequest } from 'next/server'
export async function middleware(request: NextRequest) {
return await updateSession(request) // Refresh only — no auth logic here
}
export const config = {
matcher: ['/((?!_next/static|_next/image|favicon.ico).*)'],
}
```
❌ WRONG — do NOT put auth enforcement in middleware:
```typescript
// VULNERABILITY: middleware auth check can be bypassed
export async function middleware(request: NextRequest) {
const session = await getSession() // Wrong: unreliable in Edge Runtime
if (!session) return NextResponse.redirect('/login') // Can be bypassed
}
```
## RULE 2: Auth Enforcement Belongs in Layouts and Pages
…Read the whole file at its exact version.
How to install
mdr add vibestackdev/vibe-stack/.cursor/rules/middleware-auth.mdc@sha256:53684588951982a7The line at the top of this page pins the label git:20260401.d240055, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_yww35yhu2fmlrnvl)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in vibestackdev/vibe-stack/.cursor/rules/middleware-auth.mdc since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of middleware-auth.mdc from somewhere else? Ask it: where did my middleware-auth.mdc come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Apr 1, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at middleware-auth.mdc? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (2309 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
vibestackdev/vibe-stack · 8 stars · license MIT · pushed 2026-11-17 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_yww35yhu2fmlrnvl GET https://markdownregistry.com/api/v1/resolve?ref=vibestackdev/vibe-stack/.cursor/rules/middleware-auth.mdc GET https://markdownregistry.com/api/v1/blob/53684588951982a73c1ae454fd4a9f1b89625f2b12b318c481bb135c6efcf83e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.