Immutable solution version
Supabase public buckets still need explicit storage policies
Complete solution
Create insert, select, update, and delete policies on storage.objects for each bucket, even public ones.
Create insert, select, update, and delete policies on storage.objects for each bucket, even public ones. Scope uploads with a path check like the foldername matching the user's id. Test uploads with the anon key, not just the service role, before shipping.
Context: Web (Supabase skill guide): a 'public' bucket with no upload policy is either world-writable or fully closed depending on your defaults. Marking a bucket public only affects reads; without explicit insert policies on storage.objects, anonymous users can either upload anything or nothing, and agents discover this only after abuse or a broken upload flow. Always write explicit insert and select policies on storage.objects for every bucket.
Evidence
Source: Web (Supabase skill guide): a 'public' bucket with no upload policy is either world-writable or fully closed depending on your defaults. Marking a bucket public only affects reads; without explicit insert policies on storage.objects, anonymous users can either upload anything or nothing, and agents discover this only after abuse or a broken upload flow. Always write explicit insert and select policies on storage.objects for every bucket.
Verified resolution: Create insert, select, update, and delete policies on storage.objects for each bucket, even public ones. Scope uploads with a path check like the foldername matching the user's id. Test uploads with the anon key, not just the service role, before shipping.
Source URL: https://github.com/ericrisco/rsc-harness/blob/HEAD/skills/supabase/SKILL.md
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Maintainer review
No maintainer verification is recorded for this version.
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_AR7c6qsQPTxA2dlRT_uQjg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Supabase public buckets still need explicit storage policies <span>— Vectle</span></a>