explaingit

blast-radar/blastradar-action

Analysis updated 2026-05-18

0JavaScriptAudience · developerComplexity · 2/5Setup · easy

TLDR

A GitHub Action that automatically scores every pull request's risk from 1 to 10 using AI, and can block merges when a change looks too risky.

Mindmap

mindmap
  root((repo))
    What it does
      Scores PR risk 1 to 10
      Blocks risky merges
      AI powered analysis
    Tech stack
      JavaScript
      GitHub Actions
      Anthropic API
    Use cases
      Catch risky changes before merge
      Add automated risk gate to CI
      Try scoring a diff online
    Audience
      Developers
      DevOps teams
    Setup
      Add workflow yaml file
      Needs Anthropic API key
      Set risk threshold

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 build with it?

USE CASE 1

Automatically score the production risk of every pull request in a repository.

USE CASE 2

Block a pull request from merging if its risk score is above a chosen threshold.

USE CASE 3

Paste a code diff into the companion website to get a quick risk score without any setup.

USE CASE 4

Add an AI powered safety check to an existing GitHub Actions CI pipeline.

What is it built with?

JavaScriptGitHub ActionsAnthropic API

How does it compare?

blast-radar/blastradar-action00kaku/gallery-slider-block0xkinno/vellum
Stars00
LanguageJavaScriptJavaScriptJavaScript
Last pushed2021-05-19
MaintenanceDormant
Setup difficultyeasyeasyhard
Complexity2/52/54/5
Audiencedevelopergeneraldeveloper

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

How do you get it running?

Difficulty · easy Time to first run · 5min

Requires an Anthropic API key stored as a repository secret, the README does not explain how the risk score is calculated internally.

The README does not state a license, so usage terms are unclear.

In plain English

BlastRadar is a GitHub Action, a small automated check that runs whenever someone opens a pull request on GitHub. It looks at the code changes in that pull request and gives them a risk score from 1 to 10, estimating how risky the change might be if it were released to production. If the score is too high, the check can block the pull request from being merged. Setting it up means adding a short configuration file to a repository's workflows folder that tells GitHub to run BlastRadar every time a pull request is opened. The action needs an Anthropic API key, stored as a secret in the repository settings, since it uses an AI model to analyze the code changes. There is also an optional setting called threshold, which defaults to 7, that controls the risk score at which the check fails. Once configured, the action produces two outputs for each pull request: the numeric risk score itself, and a one line verdict summarizing why that score was given. The project also has a companion website where anyone can paste in a code diff directly and get a risk score back in about ten seconds, without needing to set up the GitHub Action at all. The README for this project is fairly brief and does not go into detail about how the risk scoring itself works internally, what specific factors raise or lower a score, or what license the project is released under. The team behind it lists an email address for feedback.

Copy-paste prompts

Prompt 1
Walk me through adding this BlastRadar GitHub Action to my repository's workflows.
Prompt 2
Explain what the threshold input controls and how to pick a good value for my team.
Prompt 3
Show me how to store my Anthropic API key as a GitHub repository secret for this action.
Prompt 4
Help me understand what the risk-score and verdict outputs from this action mean.
Prompt 5
Explain how I could use the blastradar.vercel.app site to test a diff before setting up the action.

Frequently asked questions

What is blastradar-action?

A GitHub Action that automatically scores every pull request's risk from 1 to 10 using AI, and can block merges when a change looks too risky.

What language is blastradar-action written in?

Mainly JavaScript. The stack also includes JavaScript, GitHub Actions, Anthropic API.

What license does blastradar-action use?

The README does not state a license, so usage terms are unclear.

How hard is blastradar-action to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is blastradar-action for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.