Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.riftmap.dev/llms.txt

Use this file to discover all available pages before exploring further.

If I change repo X, what else breaks?
Riftmap scans a GitLab group or GitHub organization, automatically discovers how repositories depend on each other across ecosystems, and exposes a queryable dependency graph and change‑impact API. It’s designed as a first‑class tool for AI coding agents and CI pipelines that need to know the blast radius of a change before shipping it.

​
What it does

  1. Scans every repo in a connected org with a read‑only platform token.
  2. Parses ecosystem‑specific dependency declarations — Terraform module {}, Dockerfile FROM, Python requirements.txt / pyproject.toml, GitHub Actions uses:, Helm Chart.yaml, Go go.mod, npm, Kustomize, Kubernetes manifests, and more.
  3. Detects artifacts each repo produces (Docker images, Helm charts, Terraform modules, Python/Go packages…).
  4. Resolves every declaration to a known repo or artifact via a per‑ecosystem resolver chain.
  5. Stores edges in Postgres and exposes them through a small, paginated REST API.
  6. Answers GET /repositories/{id}/impact with the transitive downstream blast radius via a Python BFS.

​
Who this is for

  • AI coding agents (Claude Code, Cursor, Cline) that need cross‑repo context to plan a change without hallucinating dependencies.
  • CI pipelines that need to gate a merge on “did anything downstream just lose a contract?”.
  • Platform / infra teams that want a queryable map of how their org actually fits together, without per‑repo config files.

​
Zero per‑repo configuration

Riftmap discovers everything from the actual code in the repos you connect. There are no riftmap.yaml files, no annotations, no manifests. Connect once at the org level with a read‑only token; everything else is automatic.

​
What’s next

Quickstart

Sign up, connect your first org, and make your first API call in five minutes.

Agent integration

The recommended call pattern for AI agents: lookup → context → impact, with a freshness check rule.

Authentication

Create a workspace API key and learn the header conventions.

API reference

Full interactive reference, generated from the live OpenAPI schema.