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

nocuous

v0.4.0

Published

A static code analysis tool for JavaScript and TypeScript.

Readme

nocuous

Build Status

A static code analysis tool for JavaScript and TypeScript.

Installation

$ npx nocuous

Commands

stat

Currently the only command (which is also the default command) is stat. stat provides code toxicity statistics for a JavaScript or TypeScript project. The command expects a single input file. If this file is a JavaScript or TypeScript file, it will analyze that file plus any of its dependencies which get imported into that file for code toxicity and output the information to stdout. If the file is a .json file, it is assumed it is a tsconfig.json and uses that to determine what files to analyze. For example to run stats for a project:

$ npx nocuous index.ts

stat can take an options of -o or --output which will write the results as a CSV to the specified file.

stat also accepts multiple input files and glob patterns passed as input files.

Background

The statistics collected around code toxicity are based directly on Eric Dörnenburg's article How toxic is your code?.

The default metrics are based on what is suggested in the article. When applying to TypeScript/JavaScript there are some adaptation that is required:

| Metric | Table Label | Description | Default Threshold | | ------------------------------- | ----------- | ------------------------------------------------------------------------------------------------ | ----------------- | | File length | L | The number of lines in a file. | 500 | | Class fan-out complexity | CFAC | The number of classes or interfaces in the dependency chain for a given class. | 30 | | Class data abstraction coupling | CDAC | The number of instances of other classes that are "new"ed in a given class. | 10 | | Anon Inner Length | AIL | Class expressions of arrow functions length in number of lines. | 35 | | Function Length | FL | The number of statements in a function declaration, function expression, or method declaration. | 30 | | Parameter Number | P | The number of parameters for a function or method | 6 | | Cyclomatic Complexity | CC | The cyclomatic complexity for a function or method | 10 | | Nested if Depth | ID | The number of nested if statements. | 3 | | Nested try Depth | TD | The number of nested try statements. | 2 | | Binary Expression Complexity | BEC | How complex a binary expression is (e.g. how many && and || keywords an expression contains) | 3 | | Missing Switch Default | MSD | Any switch statements that are missing the default case. | 1 |