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

@nestling.dev/linnet

v0.0.2

Published

Get a bird's-eye view of the line counts

Downloads

18

Readme

linnet

Get a bird's-eye view of line counts in your codebase. linnet recursively scans directories, counts lines per file, and renders a colour-coded tree so you can spot oversized or deeply-nested files at a glance.

Installation

bun link

Usage

linnet [options] [paths...]

When no paths are given, the current working directory is used.

Options

| Flag | Description | |------|-------------| | -e, --exact | Show exact line counts instead of ballpark approximations | | -v, --verbose | Show all files, not just notable ones | | -a, --all | Include all files, not just git-tracked source files |

Default filters

By default linnet applies two filters so the output focuses on source code:

  1. Git-tracked only — only files listed by git ls-files are counted. If the directory is not inside a git repository, all non-ignored files are included as a fallback.
  2. Source files only — files with known non-source extensions (images, videos, audio, fonts, documents, archives, compiled objects, etc.) are skipped.

Pass --all to disable both filters and include every non-ignored file.

Ballpark vs exact mode

By default linnet displays ballpark counts (200+, 500+, 1k+, 2k+, …) and collapses groups of small files to keep the output concise. Pass --exact to see precise numbers.

Notable files

In normal (non-verbose) mode, only notable files are shown — those with 500 or more lines or a max indentation level of 16+. Files matching ignore patterns (tests, stories, specs) are also hidden. Use --verbose to disable this filter.

Configuration

Place a linnet.jsonc or linnet.json in your project (searched upward to the git root):

{
  // Show files with this many lines or more (default: 500)
  "notableLines": 500,
  // Show files with this indent depth or more (default: 16)
  "notableIndent": 16,
  // Regex patterns for files to exclude from the notable filter
  "ignorePatterns": ["\\.stories\\.[jt]sx?$", "\\.test\\.[jt]sx?$", "\\.spec\\.[jt]sx?$"],
  // In ballpark mode, collapse files below this line count (default: 200)
  "collapseBelow": 200,
  // Collapse only when there are more than this many small files (default: 5)
  "collapseThreshold": 5
}

License

MIT