Introduction to HackerOne Code for On-Premise Integrations
For integrating HackerOne Code with self-hosted (on-premise) source code provider instances.
HackerOne's PullRequest Proxy
HackerOne integrates with self-housed source code providers with the installation of PullRequest Proxy. This is a lightweight proxy server that facilitates required communications with our server.
This integration is used for HackerOne Code as well as HackerOne Code Security Audit.
Dataflow Diagram
For a visualization of how PullRequest Proxy and our systems interact with self-hosted providers, see and download the diagram below.
System Compatibility
PullRequest Proxy compatible with:
Before Getting Started
Please review the following system requirements for each of our source code management on-premises integrations below.
Be sure to send your PullRequest point of contact the version of GitHub Enterprise your team is currently running (along with any plans you have to update or change versions).
HackerOne's Pull Request Proxy for GitHub Enterprise standard integration is compatible with GitHub Enterprise 2.18 and above and optimized for GitHub API version 3.
If your team is running a prior version, we highly recommend updating. Previous versions may or may not work. Please contact us at with any issues.
If you have any custom needs or requirements that have not been discussed with HackerOne, please be sure to bring them to attention as early in the installation process as possible.
And, of course, if ever you have any questions or become blocked during the integration please get in touch with your dedicated HackerOne implementation specialist or account manager.
Be sure to send your HackerOne point of contact the version of Bitbucket Data Center (or Bitbucket Server) your team is currently running along with any plans you have to update or change versions.
HackerOne's Pull Request Proxy for Bitbucket Data Center and Bitbucket Server integration requires Personal Access Tokens which were introduced in Bitbucket Server 5.5.
For best performance, we recommend Bitbucket Server 5.10 or higher.
If your team is running a prior version of Bitbucket Server 5.5, we recommend upgrading before continuing if feasible. If not, please reach out to to your HackerOne contact to discuss options.
If you have any custom needs or requirements that have not been discussed with HackerOne, please be sure to bring them to attention as early in the installation process as possible.
And, of course, if ever you have any questions or become blocked during the integration please get in touch with your dedicated HackerOne implementation specialist or account manager.
Be sure to send your HackerOne point of contact the version of GitLab Self-Managed your team is currently running (along with any plans you have to update or change versions).
HackerOne's Pull Request Proxy for GitLab Self-Managed integration was built and optimized for GitLab 11.0 and above and GitLab API v4.0.
If your team is running a prior version, we highly recommend updating. Previous versions may or may not work. Please contact us at with any issues.
If you have any custom needs or requirements that have not been discussed with HackerOne, please be sure to bring them to attention as early in the installation process as possible.
And, of course, if ever you have any questions or become blocked during the integration please get in touch with your dedicated HackerOne implementation specialist or account manager.
Be sure to send your HackerOne point of contact the version of Azure DevOps 2019 or Azure DevOps 2020 your team is currently running (along with any plans you have to update or change versions).
HackerOne's Pull Request Proxy for Azure DevOps Server integration was built and optimized for Azure DevOps Server 2019 and above.
If your team is running a prior version, we highly recommend updating. Previous versions may or may not work. Please contact us at with any issues.
If you have any custom needs or requirements that have not been discussed with HackerOne, please be sure to bring them to attention as early in the installation process as possible.
And, of course, if ever you have any questions or become blocked during the integration please get in touch with your dedicated HackerOne implementation specialist or account manager.
Last updated