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

indent-complexity

v0.1.1

Published

Compute indentation-based complexity scores from file content and git diff.

Readme

indent-complexity

A language-agnostic code complexity analyzer. Works on any language by measuring indentation depth.

Usage

npm install indent-complexity
import { analyzeComplexity, analyzeDiffComplexity } from 'indent-complexity';

// Pass any code snippet, function of complete file to get complexity assessment:
const codeComplexity = analyzeComplexity(codeSnippet);
console.log(codeComplexity.score);

// Also supports `git diff` output to evaluate complexity for added lines (by default):
const diffComplexity = analyzeDiffComplexity(gitDiff);
console.log(diffComplexity.score);

The Score

Unfortunately none of the researchers suggests a single-metric similar to how Cyclomatic and Cognitive complexity work. So I decided to suggest one:

Σ(depth²) / lineCount

I chose depth squared weighting because:

  • Mirrors cognitive complexity principles (nested code is harder to understand)
  • Normalized by line count for cross-file comparison
  • Shallow-but-wide code scores low; deep code scores high

Default thresholds:

| Level | Score | | -------- | ------ | | low | < 4 | | medium | 4 - 10 | | high | ≥ 10 |

verbose: true returns all research-backed metrics for you to experiment and explore:

| Metric | Description | | ---------------- | -------------------------------------------- | | variance | Correlates with McCabe cyclomatic complexity | | max | Deepest nesting level | | mean | Average depth per line | | lineCount | Lines analyzed (excluding comments/blanks) | | depthHistogram | Distribution of depths |

License

MIT