Findings and verdicts go into a table you create with the SQL the app shows under the connector. The table has row level security on and grants nothing to anon, because a project’s anon key is public and findings describe weaknesses. The service_role key bypasses row level security, so use it only in a tab you trust, and prefer not to remember it.
Endpoint and protocol
| Endpoint | <Project URL>/rest/v1/<Table> (PostgREST) |
|---|---|
| Key | the service_role key in an apikey header; a JWT-form key (the older key format) is also sent as the bearer |
| Writes | an upsert on id, 500 rows per request, so sending the same scan again replaces its rows |
| Page can reach it | yes for https://*.supabase.co; a custom or self-hosted domain needs a page whose policy lists it |
Fields
| Field | Kind | Default | Notes |
|---|---|---|---|
| Project URL | address | for example https://<ref>.supabase.co | |
| service_role key | secret | Writes bypass row level security; the table grants nothing to anon. Kept in this tab unless remembered. | |
| Table | text | keryn_findings |
How keys and values are stored is on the connectors overview.
What leaves your machine
Test reads one row id from the table, which proves the address, the key and that the table exists.
Generated from the product's connector catalog (monorepo 27434c1bb57f) by tools/extract-product-facts.mjs.