Thank you for your interest in Baserow. This document explains how you can get involved.
We've decided to stop accepting unsolicited external pull requests for now. Reviewing external code contributions thoroughly takes significant time, and a growing volume of low-quality, AI-generated PRs has made the process difficult to manage for our small team.
This wasn't an easy decision, and we know it affects well-intentioned contributors. See the announcement for the full reasoning.
We will only review pull requests that were coordinated with the team in advance. PRs opened without prior coordination will be closed without review.
There's a lot you can do that we genuinely value:
- Report bugs — open a bug report with steps to reproduce and the expected behavior.
- Request features — open a feature request describing what you need and why.
- Join the discussion — share ideas, feedback, and use cases in our community forum.
Well-described issues and feedback help us shape the product and are always welcome.
If you have something specific in mind, contact us first through the community forum or the contact form at https://baserow.io/contact. If we agree the change makes sense, we'll coordinate the approach with you before any code is written — only then should you open a PR.
Note that the premium/ and enterprise/ directories contain licensed code that is not open to external contributions.
For coordinated contributions, see Code quality for our standards, linters, and testing expectations. The CI pipeline must pass and the security impact of every change must be considered.
When you submit code changes, your submissions are understood to be under the same MIT License that covers the project.
If you find a security vulnerability, please report it privately via email or the contact form at https://baserow.io/contact — do not open a public issue.
For general questions about Baserow, use the community forum.