Skip to content

Security: buildkite/test-splitter

Security

SECURITY.md

Security

Buildkite takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include Buildkite, Bazelkite, Buildbox and Packagecloud.

If you believe you have found a security vulnerability in any Buildkite repository, please report it to us as described below.

Reporting Security Issues

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them via the HackerOne Bug Bounty program. Currently, the program is private and invite only. You can request access by contacting us [directly](mailto:security@buildkite.com?subject=Vulnerability reporting invite).

If you prefer to submit without logging in, you can email us at security@buildkite.com. If possible, please encrypt your message with our PGP key. You can download it from the Buildkite Security page.

Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:

  • Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
  • Full paths of source file(s) related to the manifestation of the issue
  • The location of the affected source code (tag/branch/commit or direct URL)
  • Any special configuration required to reproduce the issue
  • Step-by-step instructions to reproduce the issue
  • Proof-of-concept or exploit code (if possible)
  • Impact of the issue, including how an attacker might exploit the issue

This information will help us triage your report more quickly.

Preferred Languages

We prefer all communications to be in English.

Policy

We reserve the right to update, modify or replace this policy. If you have suggestions on how we could improve this process, please reach out to us at support@buildkite.com.

There aren’t any published security advisories