heygrc and HackerOne Code

Different jobs, same pull request.

HackerOne Code reviews a change with a mix of human and AI review. heygrc reads the same change for the compliance control it touches. A change can be well-reviewed and still default a new feature to sharing more than it should.

Get early access by ISMS Copilot

HackerOne Code

HackerOne Code (formerly PullRequest.com) is a code review service that combines human reviewers with AI to review pull requests, with a security focus.

heygrc

heygrc reviews each pull request against the compliance frameworks your company must meet (ISO 27001, SOC 2, GDPR, and more) and cites the specific control a change touches. It is built for compliance, not code quality.

Where they do not overlap

Reviewed code that defaults a setting to public.

This change adds a sharing setting to new projects and defaults it to public so onboarding feels open. It is clean code.

projects/create.ts+1 −1

const project = await projects.create({  name,-  visibility: "private",+  visibility: "public",})

heygrcGDPR Art. 25

The code is clean and onboarding is smoother. But defaulting new projects to public is the opposite of data protection by default, which is GDPR Art. 25. heygrc is built to read a change like this against your frameworks and cite the control it touches.

Use them together

Keep HackerOne Code. Add the compliance layer.

This is not a question of which tool wins. HackerOne Code catches the bugs and quality problems heygrc never looks for, and heygrc catches the compliance issues a code review is not built to see. Running both means a pull request is checked for whether the code is good and for whether the change is compliant, two different kinds of risk, on the same diff.

heygrc does not replace your code review, and it does not certify you. It reviews changes against your frameworks and cites the control, so the compliance question is answered where the change is made. heygrc is in early access.

Get early access ← Where heygrc fits

Questions

heygrc and HackerOne Code, common questions.

Is heygrc an alternative to HackerOne Code?

Not exactly. HackerOne Code reviews your code; heygrc reviews each change for compliance against the frameworks your company must meet (ISO 27001, SOC 2, GDPR, and more) and cites the specific control it touches. They answer different questions about the same pull request, so heygrc is designed to run alongside it, not replace it.

Can I use heygrc and HackerOne Code together?

Yes. They look at different kinds of risk on the same diff: HackerOne Code on the code, heygrc on the compliance control a change touches. heygrc does not replace your code review.

What does heygrc check on a pull request?

heygrc reviews each pull request against the frameworks your company selected and cites the specific control a change touches, so the compliance question is answered in code review. heygrc does not certify you and is in early access.