Agent skill

Break

by JDArmy in JDArmy/BREAK

BREAK 业务风险枚举与规避知识库 — 查询业务安全风险、规避手段、攻击工具、威胁行为者、行业术语和典型案例,或基于知识库回答业务安全问题

Apache-2.0Auto-check: notes

Install Break

skills CLI
$ npx skills add JDArmy/BREAK --skill break -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JDArmy/BREAK break --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
break
GitHub stars
385
Token cost
~2.2k tokens
SKILL.md length
450 words
Files
6,633 (incl. scripts)
Skills in repo
1
Repo updated
First seen
Licence
Apache-2.0

At a glance

BREAK 业务风险枚举与规避知识库 — 查询业务安全风险、规避手段、攻击工具、威胁行为者、行业术语和典型案例,或基于知识库回答业务安全问题

  • Works in 3 steps: ID 查询:$query 匹配实体 ID 格式(如… → 关键词查询:$query 是简短的关键词或术语(如"验证码"、"DDoS")→… → 问题咨询:$query 是一段描述性问题(如"我们网站被爬虫爬了怎么办")→…
  • SKILL.md covers 调用方式, 工作流程, 重要原则 and 文档新鲜度门禁, plus 1 more section
  • Calls node and npm; reaches break.jd.army

What it does

Break is an agent skill from JDArmy/BREAK. BREAK 业务风险枚举与规避知识库 — 查询业务安全风险、规避手段、攻击工具、威胁行为者、行业术语和典型案例,或基于知识库回答业务安全问题

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6639 other files, including scripts (for example `.github/ISSUE_TEMPLATE/config.yml`, `.github/ISSUE_TEMPLATE/data-change.md` and `.github/actions/setup-node-env/action.yml`).

The repository describes itself as: 业务风险枚举与规避知识框架(Business Risk Enumeration & Avoidance Kownledge). The licence is Apache-2.0.

Example prompts

  • “/break”

Requirements

  • Pre-approved tools (allowed-tools): Bash

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. ID 查询:$query 匹配实体 ID 格式(如 R0001、AT0034-001 等)→ 直接精确查询
  2. 关键词查询:$query 是简短的关键词或术语(如"验证码"、"DDoS")→ 搜索模式
  3. 问题咨询:$query 是一段描述性问题(如"我们网站被爬虫爬了怎么办")→ 问答模式

What it can do on your machine

Read from SKILL.md and the folder at commit 65d1d9a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • node
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • break.jd.army

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Break loads about 2.2k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 450 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from JDArmy/BREAK at commit 65d1d9a, republished under its Apache-2.0 licence (© JDArmy). 450 words, ~2,192 tokens.

Download SKILL.mdSave it as .claude/skills/break/SKILL.md (or your agent's skills folder). This skill also uses 6632 other files; get the full folder from GitHub.
name
break
description
BREAK 业务风险枚举与规避知识库 — 查询业务安全风险、规避手段、攻击工具、威胁行为者、行业术语和典型案例,或基于知识库回答业务安全问题
allowed-tools
Bash
argument-hint
[query] — 关键词、实体 ID(如 R0001)或安全问题描述
arguments
query

BREAK 知识库 Skill

<!-- 2026-07-11:规避分类语义 key 内部迁移,无 Skill 可见调用流程变化。 -->

BREAK (Business Risk Enumeration & Avoidance Knowledge) 是一个开放的业务风险枚举与规避知识框架,包含 3416 条业务安全风险知识条目,涵盖以下实体类型:

类型数量ID 格式说明
Risk(风险)400R0001, R0001-001业务安全风险定义和影响
Avoidance(规避手段)350A0001, A0001-001应对风险的防御措施
AttackTool(攻击工具)125AT0001, AT0001-001黑灰产使用的工具
ThreatActor(威胁行为者)83TA0001, TA0001-001实施攻击的人群
Term(术语)657T0001业务安全领域术语
Case(案例)1781C0001真实的安全事件案例
BusinessDomain(业务域)20BD00行业/业务域分类

维护说明:本 Skill 的调用方式保持不变,实体统计与知识库案例事实、来源质量及数据关系补强同步更新。

调用方式

使用 Bash 执行搜索脚本。脚本路径位于 skill 目录下的 break_search.mjs。

基本命令格式
bash
node <skill_dir>/break_search.mjs "<query>" [options]

其中 <skill_dir> 为本 SKILL.md 所在的目录路径。

参数说明
参数说明
<query>必填。搜索关键词、实体 ID 或安全问题描述
--lang zh|en语言。默认自动检测:含中文字符→zh,否则→en
--type <types>逗号分隔的实体类型过滤(risks, avoidances, attackTools, threatActors, terms, cases)
--limit N每类型最大返回数,默认 5
--detail详细模式,显示完整字段和关联关系

工作流程

收到 $query 后,按以下流程处理:

第一步:判断用户意图
  1. ID 查询:$query 匹配实体 ID 格式(如 R0001、AT0034-001 等)→ 直接精确查询
  2. 关键词查询:$query 是简短的关键词或术语(如"验证码"、"DDoS")→ 搜索模式
  3. 问题咨询:$query 是一段描述性问题(如"我们网站被爬虫爬了怎么办")→ 问答模式
第二步:执行搜索
ID 查询

直接执行:

bash
node <skill_dir>/break_search.mjs "<ID>" --lang zh

返回该条目的完整详情,包括关联关系展开。直接呈现给用户。

关键词搜索
bash
node <skill_dir>/break_search.mjs "<关键词>" --lang zh

如需限定范围:

bash
node <skill_dir>/break_search.mjs "<关键词>" --type risks,avoidances --lang zh

将搜索结果整理后呈现给用户。

问题咨询(核心场景)

这是最重要的使用模式。用户描述业务安全问题时:

步骤 1:提取关键词

从用户问题中提取 1~3 组搜索关键词。例如:

  • "我们公司网站被爬虫爬了" → 关键词:"爬虫"、"数据爬取"、"反爬"
  • "用户账号总是被盗" → 关键词:"账号盗用"、"撞库"、"凭证填充"
  • "有人在我们平台薅羊毛" → 关键词:"薅羊毛"、"营销欺诈"、"黑产"

步骤 2:多轮搜索

对每组关键词分别调用搜索脚本。可以多次调用:

bash
# 第一轮:直接搜索问题关键词
node <skill_dir>/break_search.mjs "爬虫" --lang zh

# 第二轮:搜索相关风险和防御手段
node <skill_dir>/break_search.mjs "反爬" --type avoidances --lang zh

# 第三轮:如有需要,搜索其他相关领域
node <skill_dir>/break_search.mjs "数据泄露" --type risks,cases --lang zh

步骤 3:深入查询

从搜索结果中找到最相关的条目 ID,进行精确查询以获取详细信息:

bash
# 查看爬虫风险的详情和关联规避手段
node <skill_dir>/break_search.mjs R0027 --lang zh

# 查看具体规避手段的详情
node <skill_dir>/break_search.mjs A0003 --lang zh

步骤 4:综合回答

基于所有检索到的知识,给出结构化回答:

## 问题分析

根据 BREAK 知识库,你描述的问题涉及以下风险:
- **[R0027] 爬虫风险**:...(引用定义和描述)
- **[R0027-001] xxx**:...

## 防御建议

针对上述风险,BREAK 推荐以下规避手段:
1. **[A0003] 云端反爬**:...(引用定义)
2. **[A0004] 频率限制**:...
3. ...

## 可能涉及的攻击工具

- **[AT0005] 爬虫工具**:...

## 相关案例

- **[C0xxx] xxx案例**:...

> 以上信息来源于 BREAK 知识库 (https://break.jd.army/)

重要原则

  1. 永远先检索再回答:不要凭记忆回答业务安全问题,必须通过搜索脚本查询 BREAK 知识库
  2. 引用来源:回答中必须标注具体的 BREAK 条目 ID(如 R0027、A0003)
  3. 多次检索:如果第一轮搜索结果不足或不够精确,换关键词再搜
  4. 关系展开:找到相关风险后,查看其 avoidances 字段获取防御手段;找到攻击工具后,查看其 directCauseRisks 字段了解关联风险
  5. 中英文适配:如果用户使用中文提问,用 --lang zh 检索并用中文回答;反之亦然

文档新鲜度门禁

当 scripts/skill/ 搜索 / 打包脚本、导出的中英文数据包、实体字段 / 关系结构、Skill 调用参数或搜索结果格式发生变化时,必须同步更新 SKILL.md 与 SKILL_en.md。npm run validate:docs-freshness 已接入 npm run validate:data,会在相关变更缺少 Skill 文档更新时阻断。

数据治理改动也会影响 Skill 检索结果。修复 Case 的 references / summary 事实核验问题或调整 Risk 的 avoidances 关系时,应同步维护英文翻译文件,并确保前两条 Case references 尽量指向可抓取正文的稳定页面,避免 Skill 返回的案例事实无法被复核。

Term 分类使用集中注册表 key;分类修正只改中文结构源并同步实体版本,Skill 的搜索与展示会在运行时合并英文文本,无需在英文实体文件重复写入 category。

2026-07-10 的 ThreatActor 覆盖治理新增物流套利、恶意物流从业者、市场操纵、恶意量化交易、AI 智能体攻击、平台规则滥用经营和通信资源滥用服务角色,并用 audit:risk-threat-actor-coverage 区分待补关系与明确豁免风险;不改变 Skill 调用参数、搜索字段或返回格式。

2026-07-10 的 ThreatActor 引用审计将 Wikipedia 降为二手背景来源,标记机构首页、新闻索引和研究栏目等通用占位链接,并补强威胁行为者的政府、司法、学术及原始安全研究证据;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-10 的实体粒度复核清理了 R0285 的无关 Term 关系及 R0159 的重复 Avoidance 引用;该维护不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-10 的原子化治理将 A0124 拆分为 Rug Pull 链上实时检测与损失赔付/资金恢复,合并删除重复的 A0142/A0160,并删除不满足具体工具准入边界的 AT0093;关系已迁移到现有原子实体,不改变 Skill 调用参数和返回格式。

清理 Case 事实待办时,summary 只保留来源正文直接支撑的主体、时间、行为、处置和影响信息;抓取失败、仅有标题支撑或来源未覆盖的金额、数量、判决结果、监管措施等细节,应补充稳定来源后再保留,或收敛为更保守的事实表述。

补强高价值 Case references 时,优先查找执法机关、法院、检察院、监管机构、厂商公告等一手来源;若公开原始页面不可得,应使用可抓取的权威媒体、地方政法/公安频道或稳定转载交叉验证,并在 summary 中避免写入只有失效原文才支撑的细节。经检索确认原始来源不可得且已有多源支撑的项,可在待办吸纳清单中记录,不为满足门禁编造来源。

2026-07-09 的 Case P1 引用质量维护仅补强 C0066、C0130、C0248 的 references / summary 与英文翻译;未改变 Skill 调用参数、搜索字段、返回格式或实体结构。

Show full SKILL.md (182 more words)Show less

Case 事实核验使用抓取正文送入 LLM。review-case-fact.mjs 优先使用 Scrapingdog 抓取,失败或正文为空时回退本地直连抓取,并按页面声明处理 UTF-8 / GBK / GB18030;维护该脚本时需保证送审片段足够覆盖正文关键段落。大批量清理 P2 待办时按约 100 个改动设置 checkpoint,先跑 validate:data / review:changed 再提交,避免长时间积累未验证变更。

2026-07-09 的 Case P2 事实核验维护仅补强或收敛案例 summary / references / 英文翻译,不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-09 的第二批 Case P2 事实核验 checkpoint 继续收敛 C0249、C0310、C0401、C0588、C0595、C0635、C0687、C0697、C0705、C0715、C0753、C0755、C0766、C0796、C0797、C0803、C0805、C0819、C0821、C0833、C0948 的 summary、incidentTime、references 与英文翻译;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-10 的 C0354 案例维护补充法院系统来源,并将案例分类调整为更贴近事实属性的安全事件;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-10 的 C0446 案例维护补充石门县人民法院官方微信原文,并同步英文翻译;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-10 的第三批 Case P2 事实核验 checkpoint 继续补强或收敛 C0463、C0521、C0522、C0558、C0565、C0571、C0577、C0579、C0593、C0630、C0642-C0720、C0728、C0735、C0744、C0749、C0772、C0781、C0785、C0791 等案例的 summary、references、incidentTime 与英文翻译,并补充 R0290 的规避手段覆盖;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-10 的第四批 Case P2 事实核验维护继续收敛 C0654、C0657、C0684、C1160、C1198、C1235 等案例的 summary、incidentTime 与英文翻译,并将已由现有稳定来源支撑的 C0226、C0410、C0792、C0798 等项纳入待办吸纳清单;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-10 的 P1 引用质量与后续 P2 事实核验维护补强 R0081、R0196、TA0030 及 C0484、C0493、C0502、C0508、C0518、C0538、C0802、C0810、C0812、C0813、C0816、C0851、C0878、C0938、C0996、C1050、C1061、C1062、C1075、C1079、C1084、C1090、C1160、C1198 等条目的 references、summary、incidentTime 与英文翻译,并同步修正 A0225、R0267 的来源与规避关系;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-10 的 P1 引用质量补强继续替换或补充 AT0076、A0124、A0270、R0168、R0177、TA0058 的权威来源,移除 R0168 的论坛弱来源,并同步英文翻译;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-10 的 AI 数据投毒关系复核校正了 AT0108 对 R0273 的直接因果关系,移除与数据投毒无关的规避手段和 TA0058 案例/风险归因,并统一 TA0058 的训练、反馈与检索知识链路描述;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-10 的后续 Case P2 事实核验维护继续补强 C1056、C1060、C1064、C1067、C1069、C1077、C1100、C1102 等案例的可抓取来源、summary、incidentTime 与英文翻译;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-10 的 Case P2 事实核验 checkpoint 继续修订 C1482、C1484、C1485、C1488、C1490、C1493、C1495、C1498、C1500、C1501、C1504、C1505、C1511、C1512、C1518、C1519、C1521、C1523、C1528、C1531 的 summary、references、incidentTime、关系与英文翻译,并为 A0222-001 补充电商平台商品抽检专项来源;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-11 的 P2 清理批次修订 C1190、C1251、C1287、C1366、C1377、C1380、C1384、C1386、C1391、C1392、C1393、C1396、C1400、C1401、C1404、C1406、C1407、C1412、C1414、C1416 的事实摘要与来源,修复 5 个行为者一致性和 5 个风险-规避关系待办,并新增人肉刷、呼死你、溯源、DEX、隐私币、零样本语音克隆、PII、社交工程、洗号、Tor 等术语;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-07-11 的后续 P1 引用质量维护补强 C1377、C1384、C1401、C1406、C1414、C1416 的官方或事件专项来源,并将 C1384 收敛为可由来源支持的供应链篡改风险表述;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

2026-09-02 的术语 T0621(清结算)引用维护将 references 从中国人民银行清算总中心(cncc.cn)替换为中国人民银行条法司发布的《支付结算办法》(银发〔1997〕393号)官方页面,并同步英文翻译;不改变 Skill 调用参数、搜索字段、返回格式或实体结构。

review:should-extract 会用全库实体 title、keywords、aliases 以及当前实体已引用关系识别已覆盖的候选实体;维护该脚本时,应保持重复抽取建议被降噪,避免 Skill 检索结果中出现语义重复的新增实体。

实体关系图谱

理解实体间的关联关系有助于给出更完整的回答:

ThreatActor(谁)
    ├── buildAttackTools → AttackTool(自建工具)
    ├── useAttackTools → AttackTool(使用工具)
    ├── directCauseRisks → Risk(直接造成的风险)
    └── indirectSupportRisks → Risk(间接支持的风险)

AttackTool(用什么工具)
    ├── directCauseRisks → Risk(直接造成的风险)
    ├── indirectSupportRisks → Risk(间接支持的风险)
    └── avoidances → Avoidance(可被什么手段规避)

Risk(什么风险)
    └── avoidances → Avoidance(如何规避)

Case(案例)
    ├── relatedRisks → Risk
    ├── relatedAttackTools → AttackTool
    └── relatedThreatActors → ThreatActor

Term(术语)
    └── related* → 所有其他实体类型

BusinessDomain(业务域)
    ├── riskDimensions → RiskScene(按业务风险域组织风险场景)
    └── riskScenes → Risk(场景下的风险列表;父风险可代表其子风险)

© JDArmy, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6,632 other files (scripts) in the repository root of JDArmy/BREAK.

  • SKILL.md
  • .env.example
  • .github/ISSUE_TEMPLATE/config.yml
  • .github/ISSUE_TEMPLATE/data-change.md
  • .github/actions/setup-node-env/action.yml
  • .github/actions/setup-playwright/action.yml
  • .github/pull_request_template.md
  • .github/workflows/ci.yml
  • .github/workflows/deploy.yml
  • .github/workflows/link-check.yml
  • .gitignore
  • .husky/pre-commit
  • .mcp.json
  • .nvmrc
  • … and 6,619 more

Open the folder on GitHubat commit 65d1d9a

Compare with similar skills

Break next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Break compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Break this skillJDArmy/BREAK385—~2.2kAutomated safety check: NotesApache-2.0
Breakgenex-games/genex-desktop3901 repos~1.7kAutomated safety check: PassMIT
Breakopslane/verify115—~6kAutomated safety check: PassMIT
V5 Breaking Changesremotion-dev/remotion62k—~879Automated safety check: PassCustom licence
What Breakssuboss87/FDEOps953—~337Automated safety check: PassMIT
Break AI Fix Loopssickn33/agentic-awesome-skills47k1 repos~3kAutomated safety check: PassMIT

Similar skills

  • Break

    genex-games/genex-desktop

    Renders a component you choose in every state and scenario on a temporary page and stress tests it.

    390 GitHub starsUsed in 1 repo~1.7k tokens
    Testing & QAAuto-check passed
  • Break

    opslane/verify

    Try to break a change the way the real world will - network faults, restarts, two things at once, users doing things out of order - on a disposable local stack, and report what broke with a…

    115 GitHub stars~6k tokensUpdated 8 days ago
    Auto-check passed
  • V5 Breaking Changes

    remotion-dev/remotion

    Official

    Implement or review a Remotion 5 breaking change while the v4 and v5 release lines still share code.

    62k GitHub stars~879 tokensUpdated today
    Media & CreativeAuto-check passed
  • What Breaks

    suboss87/FDEOps

    Assess the impact of a proposed change on dependencies and shared infrastructure.

    953 GitHub stars~337 tokensUpdated yesterday
    Auto-check passed
  • Break AI Fix Loops

    sickn33/agentic-awesome-skills

    Stop ineffective AI coding repair loops with stable failure fingerprints, a three-attempt budget, real-path proof, negative controls, and tested rollback.

    47k GitHub starsUsed in 1 repo~3k tokens
    DevOps & CloudAuto-check passed
  • API Breaking Change Detector

    github/awesome-copilot

    Official

    Cross-references C Web API controllers/DTOs against their TypeScript/JavaScript consumers (React, Angular, Vue, Svelte, Node.js, or hand-written/auto-generated HTTP clients like Fetch, Axios, NSwag)…

    40k GitHub stars~1.7k tokensUpdated today
    Backend & APIsAuto-check passed

Questions about Break

What does Break do?

BREAK 业务风险枚举与规避知识库 — 查询业务安全风险、规避手段、攻击工具、威胁行为者、行业术语和典型案例,或基于知识库回答业务安全问题. Break is an agent skill from JDArmy/BREAK.

How do I install Break in Claude Code?

Run `npx skills add JDArmy/BREAK --skill break -a claude-code`. Or copy the skill folder (the JDArmy/BREAK repository) into .claude/skills/break in your project. Claude Code loads it when a task matches its description.

How do I install Break in Codex?

Run `npx skills add JDArmy/BREAK --skill break -a codex`. Or copy the skill folder (the JDArmy/BREAK repository) into .agents/skills/break in your project. Codex loads it when a task matches its description.

Can I use Break in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JDArmy/BREAK --skill break -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/break, .gemini/skills/break, .github/skills/break and .opencode/skills/break in your project.

What does Break need to run?

Going by SKILL.md and its folder, Break needs the command-line tools its instructions call (node and npm). Its frontmatter pre-approves these tools: Bash.

Does Break access the network?

SKILL.md names 1 domain. In commands or code: break.jd.army; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Break safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Break use?

Break is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Break use?

About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Break?

Skills that share tags, products or a category with Break: Break (genex-games/genex-desktop, 390 stars), Break (opslane/verify, 115 stars), V5 Breaking Changes (remotion-dev/remotion, 62k stars) and What Breaks (suboss87/FDEOps, 953 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Break?

JDArmy (a GitHub organization) maintains it in JDArmy/BREAK, which has 385 GitHub stars. The repository was last updated on September 28, 2026.

Source: JDArmy/BREAK on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.