For AI agent vendors

Hlido Gate — drop-in PR check for AI agent vendors.

A GitHub Action that wires Hlido into your release cycle. Fetches the latest signed Trust Attestation for your slug, posts a sticky PR comment with the current score, and blocks merges if the score drops below your configured threshold. Five lines to install. No signup required for vendors with a published Hlido review.

See the install snippet Action source on GitHub →

Install in five lines.

Drop this file at .github/workflows/hlido-gate.yml in your repo. Replace slug: cursor with your Hlido slug. That's it.

name: Hlido Gate
on: [pull_request]
permissions:
  pull-requests: write
jobs:
  hlido-gate:
    runs-on: ubuntu-latest
    steps:
      - uses: ankitkapur1992-hlido/hlido-public/actions/hlido-gate@main
        with:
          slug: cursor       # YOUR Hlido slug (replace)
          min-score: 70
          mode: warn         # change to 'fail' once you trust the signal

What the gate measures.

The gate reads the latest signed Trust Attestation we publish for every reviewed agent. That JSON document mirrors the public review — slug, score, tier, evidence count, last-tested date, links to the review and scorecard — plus an HMAC-SHA256 signature so consumers can verify the metadata hasn't been tampered with.

Score (0–100)

The Laddoo Score from your latest Hlido review. Calculated from a fixed evaluation framework so every reviewed agent is measured the same way.

Sticky PR comment

One comment per PR, replaced (not stacked) on every push. Shows score, tier, last-tested, and links back to the review and scorecard for context.

Block on regression

In mode: fail, a score below your threshold exits the action with code 1 — the PR check goes red and branch protection blocks the merge.

Soft-pass on outage

If the attestation endpoint is unreachable, the gate emits a warning and exits 0. Your CI never breaks because of a Hlido-side issue.

How thresholds work.

Pick a min-score that matches the use case. Use mode: warn for the first week or two while you watch the signal, then flip to mode: fail once you're ready to enforce.

min-score	Use case	Tier floor
70	General use — block obvious regressions	STEADY
80	Procurement-grade gate	STEADY (mid)
90	Safety-critical / regulated deploys	VITAL

Tier mapping: VITAL ≥ 90 · STEADY ≥ 70 · FADING ≥ 40 · FLATLINE < 40. Score and tier are set by independent review only — the gate is read-only.

Action source

Read the action README on GitHub.

Full input/output reference, output examples, FAQ, dispute process, and license details — on the public mirror repo where the action source lives.

Open the action README →