Skip to main content
The diff shows what changed. It does not show what ran. Agents and dependencies run code you did not write, in your CI, with your secrets. Garnet records each job at the kernel on the runners you already use: what ran, and the outbound connection each execution chain opened. It posts the result to the pull request as an Execution Profile, one per job, before anyone approves.
The Runtime Review comment on garnet-runtime-review-reference#29: one job, 12 destinations, compared with 5a6561f. Under the install step, node reached api.ipify[.]org, httpbin[.]org and ip-api[.]com

reference#29 adds one npm dependency. Its install step reached api.ipify[.]org, httpbin[.]org and ip-api[.]com. The diff names none of them.

Three parts. The GitHub App connects your repositories. The Garnet Action records your workflow. The PR comment carries one Execution Profile per job, with a link to the same profile as a logged-out public report.

Add Garnet

One App install, one workflow step. First Execution Profile on your next pull request.

See a live Execution Profile

The recorded profile behind garnet-runtime-review-reference#29. No account needed.
Then read the Execution Profile in full. Review agents and merge gates can consume the same comment; that path is a preview. Garnet records. The reviewer and repository policy decide.