heygrc and CodeScene

Different jobs, same pull request.

CodeScene looks at the health of the code, where complexity and risk accumulate. heygrc looks at compliance, the control a change touches. A change can improve the code and still break a data-subject right.

Get early access by ISMS Copilot

CodeScene

CodeScene is a code analysis tool that finds maintainability and technical-debt risks and flags risky changes on pull requests.

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 tidy change that defeats the right to erasure.

This change replaces a hard delete with a soft-delete flag, keeping the row. Soft delete is a common, reasonable pattern.

users/delete.ts+1 −1

export async function deleteUser(id: string) {-  await db.users.remove(id)+  await db.users.update(id, { deleted: true })}

heygrcGDPR Art. 17

The personal data is still there, which means an erasure request is no longer honored, and that is GDPR Art. 17. heygrc is built to catch a change that is good engineering and still removes a compliance guarantee.

Use them together

Keep CodeScene. Add the compliance layer.

This is not a question of which tool wins. CodeScene 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 CodeScene, common questions.

Is heygrc an alternative to CodeScene?

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

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