npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@systemfsoftware/stryker-js-cli

v4.0.3

Published

The stryker command-line interface — terminal framing, run-event stream, and exit handling for the @systemfsoftware mutation engine.

Readme

NPM Version Build Status License: Apache 2.0

stryker

The stryker command for the System F Software mutation engine — output meant to be read by a program.

Every run writes one NDJSON event per line to stdout and exits with a code that says which thing went wrong, so CI steps and coding agents can act on a run without scraping a progress bar.

Getting started

npm install --save-dev @systemfsoftware/stryker-js-cli
npx stryker run

With a stryker.config.json:

{
  "testRunner": "command",
  "mutate": ["src/**/*.js"],
  "thresholds": { "high": 100, "low": 80, "break": 0 }
}

Requires Node.js 20 or later.

Usage

$ npx stryker <command> [options]

Mutation testing concepts, the supported mutators, and every run option are the ones stryker-mutator.io documents. stryker --llms prints the whole command surface as one JSON object, walked from the command descriptors rather than hand-maintained.

Machine output

$ stryker run
{"kind":"stream","schemaVersion":"1.0","runId":"06FY3DSBM7TYC2RZQ0F3EGVZ88","mode":"machine","signal":"tty"}
{"kind":"phase","phase":"instrument","elapsedMs":102}
{"kind":"phase","phase":"dry-run","elapsedMs":6658}
{"kind":"plan","total":2}
{"kind":"verdict","schemaVersion":"1.0","score":100,"thresholds":{"high":100,"low":80,"break":0},"counts":{"killed":2,"survived":0,"timeout":0,"noCoverage":0},"reportFile":"reports/mutation/mutation.json"}

| kind | Emitted | Carries | | --------- | ----------------------- | --------------------------------------------- | | stream | First line of every run | runId, mode, signal | | phase | A stage begins | phase, elapsedMs | | plan | Mutants scheduled | total | | tick | Progress heartbeat | elapsedMs, completed, total | | verdict | Run finished | score, thresholds, counts, reportFile | | error | Run failed | the failure and a remediation |

The stream drains before the process exits, including on SIGINT, so the terminal line is never truncated.

Machine mode is automatic when stdout is not a TTY. STRYKER_MODE=machine sets it from the environment, and a non-empty AGENT, CLAUDECODE, or CODEX_SANDBOX selects it even on a TTY. NO_COLOR drops colour from the human path.

Exit codes

The highest pending class wins; a terminating signal outranks all of them.

| Code | Meaning | | --------- | -------------------------------------------- | | 0 | Score cleared the break threshold | | 1 | Verdict failed | | 2 | Config error | | 3 | Runtime error | | 4 | Internal error | | 128 + n | Terminated by signal nSIGINT is 130 |

Related

The mutation engine is @systemfsoftware/stryker-js-platform-node. This package is the terminal-facing half and reaches it through an injected run-event sink; it ships a command and exposes no importable API.

License

Licensed under Apache 2.0.