stryker-mutator/stryker-js

Mutation testing for JavaScript and friends

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 22nd, 2026
Created on February 12th, 2016
Open Issues & Pull Requests: 115 (+0)
GitHub issues: Enabled
Number of forks: 290
Total Stargazers: 3,145 (+0)
Total Subscribers: 26 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.1 days
Mean response time: 50.3 days
90th percentile: 144.8 days
Tracked items: 173

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "hacktoberfest" is answered fastest, typically in about 3 hours, while "⁉ Question" waits about 9 days. 40% of tracked open issues have had no activity in three months. Only 39% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 74
New in 7 days: 2
Closed in 7 days: 1
Avg open age: 307 days
Stale 30+ days: 53
Stale 90+ days: 29

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • ☠ stale (98)
  • 🐛 Bug (73)
  • 🚀 Feature request (67)
  • ⁉ Question (39)
  • hacktoberfest (16)
  • 🔧 Maintenance (15)
  • 👶 Good first issue (5)
  • help wanted (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Stryker is a mutation testing framework that evaluates the quality of your test suite by introducing deliberate code changes and checking whether your tests catch them.

Mutation testing works by modifying your source code in small, meaningful ways—such as changing operators, removing statements, or altering literals—and running your test suite against each mutated version. If your tests pass when they should fail, that reveals a gap in test coverage. Stryker automates this process for JavaScript and TypeScript projects, providing detailed reports on which mutations survived (indicating weak tests) and which were killed (caught by tests). This approach goes beyond line coverage to measure whether tests actually verify behavior.

Stryker suits projects where test quality matters: codebases with high reliability requirements, teams adopting test-driven development, or situations where you need to identify which tests are genuinely protective versus merely present. It works with popular test runners and frameworks, integrating into existing JavaScript and TypeScript workflows. The tool is particularly valuable when you want to move beyond coverage percentages and understand whether your tests would catch real bugs.

The project maintains active development with regular updates addressing new JavaScript features and test framework versions. The codebase shows consistent refinement of mutation operators and reporting capabilities. Development activity reflects ongoing engagement with the mutation testing community, including responsiveness to issues and incorporation of user feedback into the tool's evolution.