Run log · Lint baseline ·

Supabase Splinter, 17 tasks

2026-11-22_lint-splinter

The linter only detects. It cannot repair. A flag counts when the linter reports a security finding on the task's public schema.

Recorded fields

Linter
supabase/splinter main (see lint/README.md for commit)
What counts as a flag
SECURITY-category findings on public schema objects only
Tasks
17
Vulnerable tasks flagged
8
Vulnerable tasks
14
Clean tasks flagged
0
Clean tasks
3
Wall time
3 s
Hardware
RTX 4070 Ti, 12 GB

Per task

TaskWhat is wrong in the appFlagged
clean-001Correct per-user bookmarks table (control: nothing to fix) no
clean-002Blog posts readable by everyone on purpose, writable by the author only (control) no
clean-003Announcements: public read of published rows, no client writes at all (control) no
rls-001Personal notes table with RLS never enabled yes
rls-002RLS enabled but the select policy lets everyone read private orders no
rls-003Profiles: anyone, including anonymous, can update any profile yes
rls-004Shared team board: update policy USING (true) lets any member take over or rewrite another member's task yes
rls-005Comments: insert policy accepts any user_id, so a user can post as someone else yes
rls-006RLS is correct, but a SECURITY DEFINER function exposed to the API returns every invoice yes
rls-007Multi-tenant documents: the policy is right but users can insert their own membership into any org no
rls-008Public profiles expose email and phone to every signed-in user no
rls-009Notes: RLS on, no DELETE policy, so users cannot delete their own notes (secure but broken) no
rls-010Tasks table: the owner policies are granted TO anon instead of authenticated, so signed-in users see nothing no
rls-011Admin check trusts user_metadata in the JWT, which any user can edit from the client yes
rls-012App config table holds a Stripe secret key and is readable by anonymous visitors no
rls-013A reporting view over the orders table runs with the owner's rights and bypasses RLS yes
rls-014Org documents: any member can delete every document in the org; only org admins should yes