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

@linterly/cli

v0.3.3

Published

A CLI tool to check code line counts

Downloads

561

Readme

@linterly/cli

A lightweight linter that checks code line counts. Set line limits per file and per directory to detect bloated code early.

Installation

# Global
npm install -g @linterly/cli

# Project-local (recommended)
npm install -D @linterly/cli

Also available via Go:

go install github.com/ousiassllc/linterly/cmd/linterly@latest

Quick Start

# Generate a config file
npx linterly init

# Check the current directory
npx linterly check

# Check a specific path
npx linterly check src/

# Output in JSON format
npx linterly check --format json

# Override config values with CLI flags
npx linterly check --max-lines-per-file 500 --count-mode code_only

# Run without a config file (uses defaults)
npx linterly check --max-lines-per-file 500 --warning-threshold 20

# Add ignore patterns via CLI
npx linterly check --ignore "vendor/**" --ignore "*.pb.go"

# Disable default excludes
npx linterly check --no-default-excludes

Configuration

A config file is optional. Without one, Linterly runs with sensible defaults. You can override any setting via CLI flags.

Place a .linterly.yml in your project root:

rules:
  max_lines_per_file: 300
  max_lines_per_directory: 2000
  warning_threshold: 10

count_mode: all       # all | code_only
language: en          # en | ja

ignore:
  - "vendor/**"
  - "*.pb.go"

default_excludes: true

CLI flags always take precedence over config file values (CLI flags > config file > defaults).

You can also create a .linterlyignore file (gitignore format) for exclusion patterns.

Git Hooks Integration

Husky + lint-staged

{
  "lint-staged": {
    "*.{js,ts,go,py,rb}": ["linterly check"]
  }
}

Lefthook

pre-commit:
  commands:
    linterly:
      glob: "*.go"
      run: linterly check {staged_files}

Supported Platforms

| Platform | Package | |----------|---------| | Linux x64 | @linterly/linux-x64 | | Linux arm64 | @linterly/linux-arm64 | | macOS x64 | @linterly/darwin-x64 | | macOS arm64 | @linterly/darwin-arm64 | | Windows x64 | @linterly/win32-x64 |

Platform-specific packages are installed automatically via optionalDependencies.

Links

License

MIT