Riven Docs
See GitLab proof

Getting started

Installation & setup

Riven is small, but it depends on the right local and GitLab surfaces being in place before the merge gate is worth trusting.

Local prerequisites

  • Node.js 20+
  • npm
  • Git with repository history available
  • Orbit Local on PATH

Install Orbit Local

bash
curl -fsSL "https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/raw/main/install.sh" | bash
export PATH="$HOME/.local/bin:$PATH"
orbit --help

CLI naming

The product name is Riven. The current CLI and MCP binary names remain blast-radius-governor and blast-radius-governor-mcp.

Repository setup

Riven expects:

  • a Git repository with history
  • a merge-base or branch reference for --base
  • files that Orbit can index for the language surface you care about
  • a .governor.yml policy once the repo is scaffolded

GitLab setup

Riven works best when:

  • merge request pipelines are enabled
  • successful pipelines are required before merge
  • the Governor job runs on every MR pipeline

If you want CI to post comments or labels, add a masked GITLAB_TOKEN CI/CD variable. The core gate still works without it because merge is blocked by the failed job itself.

Provider setup for AI remediation

Live AI calls are optional. Dry-run artifact generation works without provider keys.

Supported live providers:

  • OPENAI_API_KEY
  • ANTHROPIC_API_KEY
  • AWS_BEARER_TOKEN_BEDROCK
  • AWS_REGION

See Configuration for the policy surface, and MCP server for external tool integration.