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

software-entropy

v1.0.0

Published

A code-smell detection CLI tool that scans repositories for common issues

Readme

Software Entropy

CI CodeQL

A code-smell detection CLI tool that scans code repositories for common issues like long functions, large files, and TODO/FIXME density.

Features

  • 🔍 Pluggable Rule System: Easy to extend with custom rules
  • 📊 Multiple Output Formats: JSON and pretty console output
  • 🎯 Common Code Smells: Detects long functions, large files, TODO/FIXME density
  • 🧪 Well Tested: Comprehensive Jest test suite
  • Fast: Efficient scanning with configurable file patterns

Installation

npm install
npm run build

Usage

Basic Usage

npm start -- <directory>

Options

  • -o, --output <file>: Output JSON report to file
  • --json: Output only JSON (no pretty report)
  • --no-pretty: Disable pretty console output
  • --max-function-lines <number>: Maximum lines per function (default: 50)
  • --max-file-lines <number>: Maximum lines per file (default: 500)
  • --max-todo-density <number>: Maximum TODO/FIXME density per 100 lines (default: 5)
  • --include <patterns>: Comma-separated glob patterns to include
  • --exclude <patterns>: Comma-separated glob patterns to exclude

Examples

# Scan current directory
npm start -- .

# Scan with custom thresholds
npm start -- ./src --max-function-lines 30 --max-file-lines 300

# Output JSON report
npm start -- ./src -o report.json

# JSON only output
npm start -- ./src --json

# Custom include/exclude patterns
npm start -- . --include "**/*.{ts,tsx}" --exclude "**/node_modules/**,**/dist/**"

Rules

Long Function Rule

Detects functions that exceed a specified line count threshold.

Default threshold: 50 lines

Large File Rule

Detects files that exceed a specified line count threshold.

Default threshold: 500 lines

TODO/FIXME Density Rule

Detects files with high density of TODO, FIXME, XXX, HACK, or NOTE comments.

Default threshold: 5% (5 per 100 lines)

Creating Custom Rules

Rules implement the Rule interface and extend BaseRule:

import { BaseRule } from './rules/Rule';
import { RuleContext, CodeSmell } from './types';

export class MyCustomRule extends BaseRule {
  name = 'my-custom-rule';
  description = 'Detects my custom code smell';

  run(context: RuleContext): CodeSmell[] {
    const smells: CodeSmell[] = [];
    
    // Your detection logic here
    if (/* condition */) {
      smells.push(
        this.createSmell(
          'Your message here',
          context.file,
          'medium', // or 'low' or 'high'
          lineNumber, // optional
          columnNumber, // optional
          { /* optional metadata */ }
        )
      );
    }
    
    return smells;
  }
}

Then add your rule to the scanner:

import { Scanner } from './scanner';
import { MyCustomRule } from './rules/MyCustomRule';

const rules = [new MyCustomRule()];
const scanner = new Scanner(rules);

Development

Build

npm run build

Test

npm test
npm run test:watch
npm run test:coverage

Project Structure

software-entropy/
├── src/
│   ├── cli.ts              # CLI entry point
│   ├── scanner.ts          # Core scanning engine
│   ├── report.ts           # Report generation
│   ├── types.ts            # TypeScript type definitions
│   ├── rules/              # Pluggable rules
│   │   ├── Rule.ts         # Base rule class
│   │   ├── LongFunctionRule.ts
│   │   ├── LargeFileRule.ts
│   │   ├── TodoFIXMERule.ts
│   │   └── index.ts
│   └── reporters/          # Report generators
│       ├── JsonReporter.ts
│       ├── PrettyReporter.ts
│       └── index.ts
├── dist/                   # Compiled output
└── tests/                  # Test files

License

MIT