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

eslint-plugin-complexijs

v0.1.0

Published

ESLint plugin reporting cognitive complexity computed by the complexijs Rust engine

Readme

eslint-plugin-complexijs

ESLint plugin that enforces a per-function cognitive complexity threshold using the complexijs Rust/WASM engine.

The analysis runs on raw source text, so it does not depend on ESLint's AST. TypeScript files work: the WASM engine can parse them directly, though you still need the usual typescript-eslint parser configured for ESLint itself if you want type-aware rules.

Install

npm install --save-dev eslint eslint-plugin-complexijs

Usage (flat config)

// eslint.config.js
const complexijs = require("eslint-plugin-complexijs");

module.exports = [
  {
    plugins: { complexijs },
    rules: {
      "complexijs/complexity": ["error", { max: 15 }],
    },
  },
];

The recommended config wires up the rule at warn with max: 15:

// eslint.config.js
const complexijs = require("eslint-plugin-complexijs");

module.exports = [
  complexijs.configs.recommended,
];

Options

| Option | Type | Default | Description | | --- | --- | --- | --- | | max | integer >= 0 | 15 | Maximum allowed cognitive complexity per function. Functions strictly above this value are reported. |

Suppressing a function

Place a // complexijs: ignore comment on the function definition line or on the line directly above it:

// complexijs: ignore
function legacyRouter(req, res) {
  // ...
}

The marker is processed by the WASM engine, not by the ESLint rule, so it works regardless of the max setting.

How complexity is scored

See the complexijs CLI README for the full scoring model. In brief: branching constructs (if, loops, switch, ternary, catch) each add 1 plus a nesting penalty. Boolean sequences add 1 per operator-type transition. Direct recursion adds 1.

Rule reference

complexijs/complexity reports one violation per function that exceeds the threshold. The message includes the function name, its score, and the current max.