Introduction to HackerOne Code for On-Premise Integrations
For integrating HackerOne Code with self-hosted (on-premise) source code provider instances.
Last updated
For integrating HackerOne Code with self-hosted (on-premise) source code provider instances.
Last updated
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 as well as .
For a visualization of how PullRequest Proxy and our systems interact with self-hosted providers, see and download the diagram below.
PullRequest Proxy compatible with:
GitHub
2.18 and above
GitHub API v3
GitLab
11.0 and above
GitLab API v4
Azure DevOps
2019 and above
Bitbucket
5.5 and above
Please review the following system requirements for each of our source code management on-premises integrations below.
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 PullRequest point of contact the version of 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 and optimized for GitHub API version 3.
Be sure to send your HackerOne point of contact the version of (or Bitbucket Server) your team is currently running along with any plans you have to update or change versions.
Be sure to send your HackerOne point of contact the version of your team is currently running (along with any plans you have to update or change versions).
Be sure to send your HackerOne point of contact the version of or your team is currently running (along with any plans you have to update or change versions).