Perseus
✦ Hackathon · GitLab Transcend — Showcase Track

Don't guess what breaks.

One mention, instant dependency impact analysis. Drop @blast-radius src/auth/tokens.py in any GitLab issue or MR and the agent maps every file that depends on your change — direct, transitive, and across projects — straight from GitLab's Orbit knowledge graph.

View on GitHub ↗ Back to products →
12
Direct dependents
47
Transitive dependents
HIGH
Risk · 59 across 3 projects
0
External services or keys
✦ Mention. Analyze. Ship.

It plugs straight into GitLab Duo.

Mention @blast-radius in any issue or MR comment and the agent queries GitLab Orbit's knowledge graph to trace every dependency chain in real time — then posts the impact, risk-scored, back into the thread where the team is already discussing the change.

GitLab DuoOrbit graphRisk-scored
GitLab MR comment
@blast-radius src/auth/tokens.py --function checkToken ── Blast Radius ────────────── DIRECT IMPACT (12 files): • src/api/middleware.py imports checkToken • src/db/sessions.py calls on init • src/ui/login.py login flow TRANSITIVE IMPACT (47 files): • src/cli/main.py → middleware.py • src/server/app.py → sessions.py RISK: HIGH — 59 dependents · 3 projects
✦ GitLab native

No external services. No API keys. Just GitLab.

Native

Orbit knowledge graph

Queries GitLab Orbit directly — traversing gl_definition nodes and gl_reference edges to map every dependency. No external service to stand up.

Native

MR comment integration

Results post as structured MR comments — direct impact, transitive impact, project impact, and risk score — in the thread where the change is discussed.

Native

CI/CD pipeline gate

One include in .gitlab-ci.yml runs Blast Radius on every merge request and blocks any that exceed your risk threshold.

Offline fixture modeDirect + transitiveCross-projectMIT licensed