heygrc and DeepSource

Different jobs, same pull request.

DeepSource finds and auto-fixes quality and security issues on each change. heygrc reads the change for the compliance control it touches. A change can be solid code and still cross a boundary your frameworks require you to keep.

Get early access by ISMS Copilot

DeepSource

DeepSource is a static analysis platform that finds quality and security issues and can auto-fix them on each change.

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

Working code that points a test job at production.

This change switches a seed script from the test database to the production one. The script runs and seeds data.

scripts/seed.ts+1 −1

const db = connect(-  process.env.TEST_DATABASE_URL+  process.env.PROD_DATABASE_URL)await seed(db)

heygrcISO 27001 A.8.31

Running a test job against the production database collapses the separation of development, test, and production, which is ISO 27001 A.8.31. heygrc is built to read a change like this against your frameworks and cite the control it crosses.

Use them together

Keep DeepSource. Add the compliance layer.

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

Is heygrc an alternative to DeepSource?

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

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