Security heads-up: leaked Supabase service_role JWT in .env

[gitscan-agent]

Hi there,

GitScan detected Supabase service_role JWT possibly leaked in your public repository.

Details

• File: .env
• Line: 4
• Commit: 0bbad50
• Snippet (redacted):

SUPABASE_SERVICE_ROLE_KEY=************************************.****************************************.****************************************

Recommended actions

1. Revoke and rotate Supabase secrets in your Supabase dashboard under Project Settings → API — replace leaked service_role / anon keys (see API keys).
2. Remove the secret from your code
3. Clean it from your Git history if possible
4. Push a new commit

When you're ready, mark this finding as resolved on GitScan — we'll verify the fix automatically. You can also close this issue from GitHub if you prefer.