heygrc
heygrc and GitGuardian

Different jobs, same pull request.

GitGuardian detects secrets, like keys and tokens, committed into code. heygrc reads the change for the compliance control it touches, a different kind of risk. A change can be a small cleanup and still leave access in place that should have been removed.

GitGuardian

GitGuardian is a security tool that detects secrets, like keys and tokens, committed into code.

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

A cleanup that skips deprovisioning.

This change removes the offboarding step that revokes a user's tokens. The code still works.

users/offboard.ts+0 −1
export async function offboard(userId: string) {  await disableLogin(userId)-  await tokens.revokeAll(userId)}
heygrcISO 27001 A.5.18

Dropping the token revocation means a departing user's access rights are not fully removed, which is ISO 27001 A.5.18 (access rights). heygrc is built to read a change like this against your frameworks and cite the control it leaves half-done.

Use them together

Keep GitGuardian. Add the compliance layer.

This is not a question of which tool wins. GitGuardian 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.

Questions

heygrc and GitGuardian, common questions.

Is heygrc an alternative to GitGuardian?

Not exactly. GitGuardian 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 GitGuardian together?

Yes. They look at different kinds of risk on the same diff: GitGuardian 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.