Skip to content

Read your first scan ​

This is a saved scan of the demo repository, not a scan of your own files. The terminal, JSON, and SARIF views below represent the same scan.

Start with one finding ​

  1. Locate it. Open the file and line next to the rule ID.
  2. Check the evidence. Read what was found and whether it applies to the purpose of that test or CI step.
  3. Review the suggested fix. Make the appropriate change yourself. Mjölnir does not apply it automatically.
  4. Verify both outcomes. Run the affected tests, then scan again. A resolved finding and a passing test run answer different questions.

For example, QA-CI-009 flags a test command piped into another tool without preserving its exit status. Review the workflow before adding set -o pipefail or splitting the commands into separate steps.

Explore the saved report ​

$ npx mjolnir-qa@latest
WORTHINESS 80/100 WORTHY
███████████████████████▓░░░░░░
Held in worthy hands — 18 findings remain.
(32 raw pts / 7 test declarations — normalized)
(capped: deduction mass 32 pts — absolute ceiling 95)
DETECTED [playwright]
▍ FIX THIS FIRST
Why it matters: 3 error findings can let a false-green or
release-blocking test issue survive review.
Next action: fix the highest score-gain item below, then
re-run the changed scope.
$ mjolnir --scope changed
+8 pts QA-CI-009 · .github/workflows/ci.yml:10
+8 pts QA-CI-009 · .github/workflows/ci.yml:10
+8 pts QA-CI-009 · .github/workflows/ci.yml:26
▍ DIAGNOSTICS BY CATEGORY
QA-CI ███████████▓░░░░ 76
QA-PW ██████████████▓░ 95
QA-TEST ████████████████ 97
▍ WHERE POINTS WERE LOST
╭─────────────────────────────────────────╮
│ 3 × error − 24 │
│ 3 × warning − 7 (evidence-discounted) │
│ 12 × info − 1 (evidence-discounted) │
╰─────────────────────────────────────────╯

Try it on your repository ​

Follow Getting started for prerequisites and the first command. For the meaning of the verdict and deductions, read Scoring.

Released under the MIT License.