Skip to Content
Baseera Docs

Responsible disclosure

How to report a security problem in Baseera and what to expect.

If you find a vulnerability, please do not open a public issue.

How to report

Use Report a vulnerability on the Baseera repository's Security tab. It is GitHub private vulnerability reporting, so only the maintainers see the report.

Include:

  • what you found;
  • how to reproduce it;
  • what it could allow.

What to expect

We acknowledge reports within two working days.

No security email address is published here. Use the private reporting channel above.

Scope

The things the platform guarantees are listed in Security and its sub-pages. A report that shows one of them failing is the most useful kind, for example:

  • one tenant or organization reading another's data;
  • a token accepted that should be refused;
  • a provider key reaching a log, a response or the browser;
  • an outbound request reaching a private address;
  • an audit entry that can be edited or removed.

If you are a contributor

  • A new table needs row-level security and, if the API should write to it, a function that validates its input, checks the caller's role and pins search_path.
  • A new security definer function that signed-in users may call must be added to the reviewed list in supabase/tests/security_invariants.test.sql on purpose.
  • Never log a key, a token, a prompt or a provider response body.

Next steps

On this page