CLI tool
stryker-mutator/stryker-js avatar
stryker-mutator/stryker-js

The dependency named typescript is an alias for something else

Mutation testing for JavaScript and friends

3,407 stars317 forksTypeScriptApache-2.0

At a glance

What is it?
stryker-js is a mutation testing tool for JavaScript, and its readme is a hundred and seventy-four words that hand you two defaults and point at a website four times. Its dependency on TypeScript is an npm alias resolving to a different package at a different major version, with a second compiler installed under a scoped name, and three configuration files at the root including one built only for the linter.
Who is it for?
stryker-js suits a team that already trusts its test suite and wants to know which tests are actually load bearing, since it answers that question by breaking your code on purpose and seeing who notices. Three things to know before you switch it on.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • stryker-mutator/stryker-js3,407 ★ · +262
Star history
Repository2026-09-242026-11-21
stryker-mutator/stryker-js3.1k3.4k

262 Stars in the last 58 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The epigraph is a dialogue about mutants, which is the whole project

The readme opens with two lines of dialogue between two named characters before it says anything about the software.

One of them remarks that someone who hates mutants keeps strange company. The other replies that they serve their purpose, as long as they can be controlled.

That is the entire idea of the tool as a joke. Mutation testing works by taking your code, changing it in small ways that a test ought to catch, and checking whether your suite actually catches it. A change that survives is a mutant, and a suite with too many survivors has a coverage number that means less than it appears to.

The character name is the tool's name, which is also the package's name, and the mutator is the product. It is a small thing, but it is the only part of this repository that explains what the tool is for, because the rest of the front page hands you two default settings and four links to a website.

So the joke is also the documentation, and you have to catch it before you know what the defaults do.

The dependency called typescript points at another package

There is a line in this repository's dependency list that will stop you, and it is worth reading twice.

The dependency named typescript is not the typescript package. It is an alias, and the alias resolves to a different package entirely, at a version one major behind what you would expect from the name.

A second entry then aliases the real typescript package under a scoped name of its own, at the newest major.

So this repository installs two compilers, from two different packages, at two different major versions, and reaches them under two names. Whichever one the code imports as typescript is not the package most people assume it is.

There is a reasonable reason for doing this rather than a mistake, and the next section is the reason. But it is also the kind of decision that only makes sense inside a project whose entire purpose is measuring whether its own tests notice anything, and it means a newcomer who reads the dependency list and installs the obvious package will not get the same compiler.

Two compilers and three configuration files, one of them only for linting

The root has three TypeScript configuration files, and their names are the explanation for the aliases.

One is the ordinary build configuration. One is named for settings, which is the shared base the others extend. And one is named for linting.

A separate configuration for the linter means the linter runs against different compiler options from the build, and having two compilers available under different names is what makes that possible: the build uses one, the analysis uses the other, and neither has to pretend to be the other.

That is a considered arrangement, and it is also the reason the alias is not accidental. The cost is that a contributor reading a type error from the linter may be looking at output from a compiler version the build never uses.

The lint tooling around it is modern and flat: the linter itself and its shared configuration package on recent majors, the TypeScript lint plugin and its utilities sharing a single version, and a formatter with two plugins bridging the two tools so they do not argue with each other.

The two defaults are a test command and two directory names

Here is the entire zero-configuration behaviour of this tool, in full, from the front page.

Install the core package as a development dependency. Run the tool. It will use the standard npm test command as your test command, and it will search two directories for files to mutate.

code
pnpm add --save-dev @stryker-mutator/core
# Only for small projects:
npx stryker run

That is it. No inference from your project layout, no detection of your test runner, no reading of your configuration. A specific command and two specific directory names.

Those defaults are the first thing worth knowing about this tool and they are the only configuration details in the readme. Everything else is a link: the quickstart, the usage reference, the list of mutators, and the configuration reference.

Which is a defensible choice for a project with a documentation site, and an unhelpful one for anyone evaluating the tool from its repository. The four links are all to the same site, and the readme is otherwise a joke and two bullet points.

The quick start is labelled as being only for small projects

The command block that contains those two defaults is introduced with a qualification, and it is the most useful sentence in the readme.

It says that for small JavaScript projects you can try this command. The word only is doing the work: the zero-configuration path is explicitly scoped, and the repository does not pretend otherwise.

This is worth reading alongside what the tool does. Mutation testing multiplies your test suite: every mutant is a run of your whole suite against slightly broken code. On a project with thousands of mutants that is not a slow build, it is a build that does not finish in your working day. A tool that tells you on its front page that the quick start is for small projects is being more useful than one that does not.

The usage line at the bottom of the readme shows the shape of the full interface: a command, some options, and an optional configuration file. So the escape from the defaults is a config file, not more flags.

The answer to why a monorepo is a link to another company's design document

This repository is a monorepo and it says so, and then it addresses the two objections in four sentences.

First: all official packages are maintained here, and if you are new to monorepos the instruction is not to be scared, with the packages in one folder. Second: if you want to know why they chose a monorepo, read another project's design document on monorepos, because they chose it for the same reasons.

The reasoning is outsourced to a well-known JavaScript project's write-up. That is a confident choice rather than a lazy one, and it tells you something real about the project's culture: the maintainers are willing to point at somebody else's argument instead of making their own.

The tree backs the description up. There are two workspace tools configured side by side, a workspace file for one editor committed at the root, submodules, a dev container, a lint configuration for the whole tree, and separate directories for end-to-end tests, performance benchmarks, tasks and documentation. Every one of those is a consequence of running many packages in one repository, and the readme's four sentences are an accurate summary of them.

It runs mutation testing on itself, with a score badge and two CI configurations

The first link on the front page is not documentation, it is a dashboard. It points at a report viewer scoped to this repository and its default branch, which means the project's own mutation score is published as a build artefact rather than a claim in a readme.

There is also a configuration file at the root for the tool to run on itself, named as the parent configuration for the workspace. So the project that measures test quality measures its own, and publishes the number where anyone can see it.

The badge image beside it is named with a specific figure, which is the kind of detail worth knowing: whether that number is a score or a threshold, the filename is the only place on the front page where a target appears at all.

Alongside all of that, the root carries two continuous integration configurations in two different directories, one for each forge, plus a dependency update bot configuration and a changes file. A project that puts mutation testing in its own pipeline has already decided that test quality is a gate rather than a report, and the rest of the tooling is consistent with that.

Editorial conclusion

stryker-js suits a team that already trusts its test suite and wants to know which tests are actually load bearing, since it answers that question by breaking your code on purpose and seeing who notices. Three things to know before you switch it on. It is slow by construction, and the readme's own zero-configuration path is marked as only for small projects, so start with one directory. Read the two defaults it will assume if you configure nothing, because they are a specific test command and two specific directories rather than anything inferred from your project. And keep it out of the inner loop: this is a build-time gate, not something to run on every save.

Frequently asked questions

what is stryker js

The JavaScript implementation of Stryker, published as a monorepo of packages on the package registry, with the core package named after the mutator. It checks a test suite by making small changes to the code and seeing which changes the tests fail to notice.

What does mutation testing do?

This repository does not define it, and points to its website instead. What the repository does show is the operational shape: it runs your test command against mutated copies of your source, searches two directories by default, and reports which mutations survived.

What does Stryker do?

In this repository it is a mutation testing tool for JavaScript, maintained as a monorepo. With no configuration at all it uses the standard npm test command and looks for files to mutate in two named directories, and the readme marks that quick start as being only for small projects.

How is JavaScript used in testing?

Not addressed here. What the repository does is pick its own stack: a TypeScript codebase built with two aliased compilers, tested with two runners plus a snapshot library and a mocking library, formatted and linted through two tools, with end-to-end tests driven through a browser automation package.

What are the three pillars of Stryker corporate responsibility?

Not a question this repository concerns itself with. It is the source repository for a mutation testing tool, and its front page is a published mutation score, a joke, two default settings, and four links to the project's website.

Official sources

  1. License: Apache-2.0
  2. Project website
  3. README
  4. Releases
  5. stryker-mutator/stryker-js on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/stryker-mutator-stryker-js.svg)](https://hysenlabs.com/projects/stryker-mutator-stryker-js)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/stryker-mutator-stryker-js.svg)](https://hysenlabs.com/projects/stryker-mutator-stryker-js)

Was this useful?