Coverage Gate Lint — find coverage gates that cannot fail

It reads a coverage configuration file — codecov.yml, .coveragerc, setup.cfg, pyproject.toml, a Jest or Vitest config, or a CI workflow — and reports every line that makes the coverage gate incapable of failing a build. Fourteen rules cover informational statuses, missing fail_under, empty thresholds, whole-tree omits and discarded exit codes.

Platform and CI engineers who own a monorepo's test pipeline, and the teams preparing EU Cyber Resilience Act or NIS2 evidence this quarter. If someone asks you to show that your coverage gate blocks merges, and your answer depends on a config file you did not write, this is aimed at you.

YAML linters check syntax, and every one of these settings is valid syntax. Codecov and coverage.py accept them without warning, because each is a legitimate option someone deliberately wants. A chatbot can explain one snippet you paste, but it will not tell you which of the config files in your repo are the disarmed ones.

Free with no licence key: the file you have open is checked against all fourteen rules, with line numbers and the fix for each. Nothing is withheld or watermarked. The paid tier changes scope instead: it sweeps every coverage config and workflow in the workspace and exports a dated report of which gates block.

A contract CI or DevOps engineer bills about $150 per hour, and opening every coverage config and workflow in a mid-sized monorepo to judge whether each gate can fail is most of an afternoon. The extension is $29 once, one licence key per person or CI seat, with a 7-day full refund.