chore: upgrade splinter to latest commit#684
Merged
Conversation
Add two new security lint rules from supabase/splinter: - sensitiveColumnsExposed: detects tables exposed via API with sensitive columns without RLS - rlsPolicyAlwaysTrue: detects overly permissive RLS policies using USING (true) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sensitiveColumnsExposed: detects tables exposed via API with potentially sensitive columns (PII, credentials, financial info) without RLS protectionrlsPolicyAlwaysTrue: detects overly permissive RLS policies usingUSING (true)orWITH CHECK (true)for UPDATE, DELETE, or INSERT operationsTest plan
cargo clippypasses🤖 Generated with Claude Code