Does this repo's CI actually block?
Enter a public GitHub repository. zanadir reads its CI configuration and reports which security and quality checks are missing, and which are there but can't fail the build.
Runs in your browser. zanadir fetches the repository's files from GitHub and sends them nowhere else. Each scan uses 3 of the 60 requests an hour GitHub allows without signing in.
Present, but can't block
A check here runs, yet a failure doesn't stop the change.
Missing
No check for these anywhere in the CI configuration.
Covered
Not applicable
The repository has nothing for these to check.
Add a badge to the README
Link badge
No setup, and never out of date: anyone who clicks it gets a fresh scan.
Live score
Shows the score, kept current by the GitHub Action. Save this as .github/workflows/zanadir.yml. It grades every push and pull request, and on the default branch publishes the score to a badges branch that holds only the badge file.
Then add the badge. Today it would read ; it appears once the workflow has run on the default branch.
If a ruleset covers every branch rather than only the default one, exclude badges from it.
Close the gaps
Get ready-to-paste configuration for them with the CLI: zanadir fix --repo owner/name