We don't stop at keeping your code safe. When your team's developers use Sourcegraph, they can discover and use your own security best practices much more easily in your own code. Your team can also more easily enforce security standards during code review.
If you have specific questions or concerns, contact us at [email protected].
If you think you have discovered a security vulnerability in our product, please follow our instructions on how to report a security vulnerability.
Sourcegraph instances that host private code are typically deployed on-premise and therefore Sourcegraph employees have no access to customer data or code.
Self-hosted Sourcegraph instances do not send any customer code to other servers.
Additionally, other than the email address of the initial installer (for customer support, security, and product notification purposes), Sourcegraph never sends any private user data, such as usernames or email addresses, or other specific data to any other servers, including to sourcegraph.com.
Learn more in our pings documentation.
Sourcegraph can be configured to enforce repository permissions from code hosts. Unit and integration tests protect the correctness of these permissions checks.
When running Sourcegraph on your own infrastructure, all application logs are stored locally, and never shared with Sourcegraph. Sourcegraph employees and contractors never have access to your Sourcegraph instance, or any of its data, unless explicitly shared for troubleshooting purposes.
We maintain the following policies for sourcegraph.com data and any data provided via email or other support channels:
When running Sourcegraph on your own infrastructure, you are protected by the network security policies enforced by your infrastructure environment.
On sourcegraph.com, we maintain the following policies:
Sourcegraph supports HTTPS encryption when deployed on your own infrastructure.
On sourcegraph.com, we maintain the following policies:
Code reviews are mandatory for all code changes to our product. Security-sensitive pull requests must undergo review by the proper security code owner. Furthermore, internally, we use our own product to provide critical context during code reviews (such as identifying dependencies of modified code).
We use a number of static analysis tools to identify security risks in development, including the following:
Sourcegraph follows commonly recognized best practices for updating software dependencies.
Customers are encouraged to update to the latest release of Sourcegraph every month. This will ensure that their Sourcegraph instance has the latest security-related updates. New releases are published on the 20th of every month, so customers that wish to stay up-to-date can set monthly calendar reminders, or subscribe to Sourcegraph emails to receive the following updates: