heygrc and Qodana

Different jobs, same pull request.

Qodana brings JetBrains' static analysis into CI, checking the code for quality and correctness issues. heygrc reads the same change for the compliance control it touches. A change can be clean code and still open a path in from outside your system boundary.

Get early access by ISMS Copilot

Qodana

Qodana is JetBrains' code-quality platform. It runs IDE-grade static analysis in your CI and reports issues 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

Clean code that opens a boundary to the world.

This change sets CORS to allow any origin so a partner integration works. It is a small, valid config change.

server/cors.ts+1 −1

app.use(cors({-  origin: "https://app.example.com",+  origin: "*",}))

heygrcSOC 2 CC6.6

The config is valid and unblocks the partner. But allowing any origin widens access from outside the system boundary, which is SOC 2 CC6.6 (boundary protection). heygrc is built to read a config change like this against your frameworks and cite the control it touches.

Use them together

Keep Qodana. Add the compliance layer.

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

Is heygrc an alternative to Qodana?

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

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