git404hub

what is gh-blast-radius fr?

divyamk1234/gh-blast-radius — explained in plain English

Analysis updated 2026-05-18

0PythonAudience · ops devopsComplexity · 3/5LicenseSetup · moderate

tl;dr

gh-blast-radius maps which repos depend on a shared GitHub Actions workflow and blocks pull requests that would break them.

vibe map

mindmap
  root((gh-blast-radius))
    What it does
      Maps workflow dependencies
      Blocks breaking PRs
      Impact reports
    Tech stack
      Python
      GitHub Actions
      PyYAML
      networkx
    Use cases
      Find workflow consumers
      Diff workflow versions
      CI breaking change checks
    Audience
      Platform teams
      DevOps engineers
      GitHub org admins

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Find every repository and job that depends on a specific shared GitHub Actions workflow before changing it.

VIBE 2

Run an automatic pull request check that blocks a merge if it would break downstream consumer repos.

VIBE 3

See which shared workflow across an organization has the widest blast radius, meaning the most consumers.

VIBE 4

Diff two versions of a shared workflow file to find exactly which callers would break.

what's the stack?

PythonGitHub ActionsPyYAMLnetworkx

how it stacks up fr

divyamk1234/gh-blast-radius0xallam/my-recipe0xhassaan/nn-from-scratch
Stars00
LanguagePythonPythonPython
Last pushed2022-11-22
MaintenanceDormant
Setup difficultymoderatemoderatemoderate
Complexity3/52/54/5
Audienceops devopsgeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires a GitHub Personal Access Token with repo scope to read workflow files across the organization.

MIT license, use freely including commercially as long as the copyright notice is kept.

in plain english

gh-blast-radius is a command line tool and GitHub Action that answers one question for platform and developer experience teams: if I change this shared GitHub Actions workflow, what breaks. Many organizations build reusable workflows and composite actions that dozens or hundreds of other repositories depend on, but until now there was no easy way to see which repos use a shared workflow, what inputs or secrets they pass to it, or what would break if it changed. Teams often find out only after merging a change that they broke many downstream projects at once. The tool works by crawling every repository in a GitHub organization through the GitHub API and reading the workflow YAML files in each one. It parses out the inputs, secrets, and uses references in those files, then builds a directed graph connecting shared workflows to the repositories that call them, including the exact inputs each caller passes. This graph is saved locally as a JSON file, and the tool caches file contents by their SHA so later scans do not need to reread files that have not changed. Once the graph exists, several commands let you query it: scan builds or refreshes the graph, consumers lists every repository that depends on a specific shared workflow, deps shows what shared workflows a given repository depends on, stats reports which shared workflow has the widest blast radius, and diff compares two versions of a workflow file to flag exactly which consumers would break from a proposed change. The most useful setup runs gh-blast-radius as a Pull Request check inside GitHub Actions. When someone edits a shared workflow file, the action scans the organization, diffs the old and new versions, and if it finds a breaking change it posts a comment on the Pull Request naming who would be affected and fails the CI check, blocking the merge before it can break other teams' pipelines. Installation is a single pipx or uv command, and using it requires a GitHub Personal Access Token with repo scope so it can read workflow files across the organization. The project is released under the MIT license.

prompts (copy fr)

prompt 1
Set up gh-blast-radius to scan my GitHub organization and build the dependency graph of shared workflows.
prompt 2
Add the gh-blast-radius composite action to my shared-workflows repo so pull requests get checked automatically.
prompt 3
Show me which repos consume my-org/shared-workflows/.github/workflows/build.yml using gh-blast-radius.
prompt 4
Use gh-blast-radius diff to check if adding a required input would break any consumers.
prompt 5
Explain how to set up the ORG_READ_TOKEN secret needed by gh-blast-radius.

Frequently asked questions

what is gh-blast-radius fr?

gh-blast-radius maps which repos depend on a shared GitHub Actions workflow and blocks pull requests that would break them.

What language is gh-blast-radius written in?

Mainly Python. The stack also includes Python, GitHub Actions, PyYAML.

What license does gh-blast-radius use?

MIT license, use freely including commercially as long as the copyright notice is kept.

How hard is gh-blast-radius to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is gh-blast-radius for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.