file-uploads Cursor ruleA
file-uploads from vibestackdev/vibe-stack is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add vibestackdev/vibe-stack/.cursor/rules/file-uploads.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/file-uploads.mdc- Versions recorded
- 1
- Latest version
- git:20260401.d240055, committed Apr 1, 2026
- Size
- 3,035 bytes
- Repository stars
- 8
- License
- MIT
Image and file upload patterns — prevents insecure client-side uploads and missing file validation.
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
# File Upload Security Rules
## RULE 1: NEVER Upload Directly From Client to Supabase Storage With the Anon Key
Client-side uploads with the anon key allow users to upload to any bucket path.
Always generate a signed upload URL server-side, scoped to the authenticated user.
✅ CORRECT — server generates signed URL:
```typescript
// Server Action
'use server'
import { createClient } from '@/lib/supabase/server'
export async function getUploadUrl(filename: string, contentType: string) {
const supabase = await createClient()
const { data: { user } } = await supabase.auth.getUser()
if (!user) throw new Error('Unauthorized')
// Scope the path to the user's ID — prevents path traversal
const path = `${user.id}/${Date.now()}-${filename}`
const { data, error } = await supabase.storage
.from('uploads')
.createSignedUploadUrl(path)
if (error) throw error
return { signedUrl: data.signedUrl, path }
}
```
❌ WRONG — direct client upload with anon key:
```typescript
// Client Component -- exposes storage to manipulation
const { data, error } = await supabase.storage
.from('uploads')
.upload(`${filename}`, file) // No user scoping — any path writable
```
…Read the whole file at its exact version.
How to install
mdr add vibestackdev/vibe-stack/.cursor/rules/file-uploads.mdc@sha256:78c9ed3ce9965379The 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_rmscf3joqkaa6zot)
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/file-uploads.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 file-uploads.mdc from somewhere else? Ask it: where did my file-uploads.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 file-uploads.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 (3035 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_rmscf3joqkaa6zot GET https://markdownregistry.com/api/v1/resolve?ref=vibestackdev/vibe-stack/.cursor/rules/file-uploads.mdc GET https://markdownregistry.com/api/v1/blob/78c9ed3ce9965379eaece8367cafcbf3648be04354ba57d50c8b06ded0ecb58a
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.