fix: enforce RLS on internal metrics table - #26
Merged
Conversation
SamOkampo
marked this pull request as ready for review
August 11, 2026 20:58
|
ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing |
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
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
Hardens the internal
public.airdows_daily_metricstable so recreating or initializing it cannot leave browser-facing Supabase roles with direct table access.Changes
public.airdows_daily_metricsMetricsStore.initialize()anonauthenticatedpostgresorservice_roleScope
Only:
metrics-store.jstest/metrics-store-security.test.jsNo changes to WebRTC, Socket.IO, TURN, transfer logic, PR #25, analytics, or the admin dashboard.
Production context
The Supabase table was manually hardened already by enabling RLS and removing
anon/authenticatedprivileges. This PR makes that security posture repeatable if the table is recreated or initialized again.Validation
GitHub Actions should run the repository unit, syntax, whitespace and critical E2E checks on this PR. No public RLS policies are introduced.