Skip to content
Back to search

mootant

🐮 Mutation testing tool that ships with an agent skill for finding and fixing weak tests

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 20 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/azat-io/mootant with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/azat-io/mootant'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/azat-io--mootant/badge.svg)](/listings/azat-io--mootant)

HTML

<a href="/listings/azat-io--mootant"><img src="/api/listings/azat-io--mootant/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

> **Early development.** Expect breaking changes.

You need passing tests on **Vitest 5** (Node.js 22.12+, no browser mode), **Jest 29.7+** or **Node Test** (Node.js 20.19+ or 22.12+). See [compatibility](https://mootant.org/guide/compatibility) for other limits.

Install Mootant and point it at your source code:

npm install -D mootant
npx mootant run src

Mootant never writes to your source files. The report lists the mutants that survived, those no test reached and any errors. To see the mutants without running any test, use `npx mootant list src`.

Follow the [getting started guide](https://mootant.org/guide/getting-started) to turn a surviving mutant into a test that catches it.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

readme.md · README · 132 lines
  1. # Mootant
  2. <picture>
  3. <source
  4. srcset="https://raw.githubusercontent.com/azat-io/mootant/main/assets/logo-light.svg"
  5. media="(prefers-color-scheme: light)"
  6. />
  7. <source
  8. srcset="https://raw.githubusercontent.com/azat-io/mootant/main/assets/logo-dark.svg"
  9. media="(prefers-color-scheme: dark)"
  10. />
  11. <img
  12. src="https://raw.githubusercontent.com/azat-io/mootant/main/assets/logo-light.svg"
  13. alt="Mootant Logo"
  14. align="right"
  15. height="160"
  16. width="160"
  17. />
  18. </picture>
  19. [![Version](https://img.shields.io/npm/v/mootant.svg?color=b8f12a&labelColor=f4f2ec)](https://npmjs.com/package/mootant)
  20. [![Code Coverage](https://img.shields.io/codecov/c/github/azat-io/mootant.svg?color=b8f12a&labelColor=f4f2ec)](https://codecov.io/gh/azat-io/mootant)
  21. [![GitHub License](https://img.shields.io/badge/license-MIT-232428.svg?color=b8f12a&labelColor=f4f2ec)](https://github.com/azat-io/mootant/blob/main/license.md)
  22. Find the gaps in your tests.
  23. Mutation testing for JavaScript and TypeScript. Mootant makes small changes to
  24. your code, called mutants, and runs your tests. If they still pass, the mutant
  25. survives, which points to a test that is missing or too weak.
  26. ## See what your tests miss
  27. Coverage shows that a line ran, not that a test would notice it change. In the
  28. [sample shop](https://github.com/azat-io/mootant/tree/main/docs/demo), the tests
  29. run every line and branch of `src/discount.ts`, yet all of them still pass after
  30. Mootant makes this change:
  31. ```diff
  32. - if (total >= 100 || isMember) {
  33. + if (total > 100 || isMember) {
  34. ```
  35. The tests cover small orders, large orders and members. None checks a
  36. non-member's order of exactly 100, where this change removes the discount. That
  37. is why this mutant survives.
  38. Mootant shows the change, suggests `test/discount.test.ts` as the file to extend
  39. and prints the mutant's id, so `--mutant q31p` re-checks it after you add the
  40. missing test.
  41. ## Why Mootant
  42. - **Use your existing tests.** Mootant works with Vitest 5, Jest 29.7+ and Node
  43. Test, using your project's test configuration. With Vitest, it also tests Vue
  44. and Svelte components.
  45. - **Find hidden gaps.** Mootant mutates numbers, return values, `await`s and
  46. regular expressions, not just operators.
  47. - **Filter out noise.** Mootant skips duplicate and likely equivalent mutants,
  48. and by default leaves out loop changes it expects to hang.
  49. - **Follow each finding.** Reports show the code change and a suggested test
  50. file. Re-check one mutant as you improve the tests, or export JSON for tools
  51. and agents.
  52. - **Check your next change.** Mootant caches verdicts between runs. In CI, check
  53. changed lines with `--since` and set a passing score with `--threshold`.
  54. ## Getting started
  55. > **Early development.** Expect breaking changes.
  56. You need passing tests on **Vitest 5** (Node.js 22.12+, no browser mode), **Jest
  57. 29.7+** or **Node Test** (Node.js 20.19+ or 22.12+). See
  58. [compatibility](https://mootant.org/guide/compatibility) for other limits.
  59. Install Mootant and point it at your source code:
  60. ```sh
  61. npm install -D mootant
  62. npx mootant run src
  63. ```
  64. Mootant never writes to your source files. The report lists the mutants that
  65. survived, those no test reached and any errors. To see the mutants without
  66. running any test, use `npx mootant list src`.
  67. Follow the [getting started guide](https://mootant.org/guide/getting-started) to
  68. turn a surviving mutant into a test that catches it.
  69. ## HTML report
  70. Browse each mutant in its code, see what your tests reach and find the files
  71. with the lowest scores. Add `--html` to write `.mootant/report.html`, a single
  72. file that opens offline:
  73. ```sh
  74. npx mootant run src --html
  75. ```
  76. Add `.mootant` to `.gitignore`: the report holds your source code.
  77. <a href="https://mootant.org/report/demo">
  78. <picture>
  79. <source
  80. srcset="https://raw.githubusercontent.com/azat-io/mootant/main/docs/public/report-overview-dark.webp"
  81. media="(prefers-color-scheme: dark)"
  82. />
  83. <img
  84. src="https://raw.githubusercontent.com/azat-io/mootant/main/docs/public/report-overview-light.webp"
  85. alt="Mootant report for a sample shop, showing surviving mutants and the mutators its tests miss."
  86. width="900"
  87. />
  88. </picture>
  89. </a>
  90. [Explore the demo report](https://mootant.org/report/demo) or
  91. [learn about the HTML report](https://mootant.org/guide/report).
  92. ## Documentation
  93. - [CLI reference](https://mootant.org/guide/cli)
  94. - [Configuration](https://mootant.org/guide/configuration)
  95. - [Mutators](https://mootant.org/mutators) and
  96. [ignore comments](https://mootant.org/mutators#ignore-mutants)
  97. - [Supported runners and frameworks](https://mootant.org/guide/compatibility)
  98. ## Contributing
  99. See
  100. [Contributing Guide](https://github.com/azat-io/mootant/blob/main/contributing.md).
  101. ## License
  102. MIT &copy; [Azat S.](https://azat.io)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.