check-risk
A CLI and GitHub Action that assesses code-change risk using deterministic rules and TypeSafe Jev, recommending checks and reviewers before merge.
How it uses Jev
Your policy defines the sensitive parts of your repository. Deterministic checks catch changed paths, new dependencies, large diffs, and missing test changes. TypeSafe Jev adds semantic signals about the behavior being changed. Every contribution leads back to a named rule.
Getting started
Clone moezubair/check-risk and open a terminal in the clone. Install Node.js 22 or newer and Git first, then run:
Source: community catalog. Details and metrics reflect the published community snapshot and are not a performance endorsement. Documentation details extracted from GitHub · the README.