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

@import-lint/cli

v0.1.9

Published

Enforces directory-level encapsulation in TypeScript/JavaScript: tag an export @package and only files in or below its directory can import it. Fast Rust CLI, no TypeScript compiler or ESLint needed (a port of eslint-plugin-import-access)

Readme

@import-lint/cli

ImportLint enforces directory-level encapsulation in TypeScript and JavaScript: tag an export @package in its JSDoc, and only files in that directory (or nested below it) — its "package" — can import it; ImportLint flags every import that breaks the rule. It's a small, fast Rust CLI, so it runs without a TypeScript compiler or ESLint, and stays fast on large codebases (it's a drop-in replacement for eslint-plugin-import-access).

See the main repository README for the full pitch, a concrete example, and the guides — this page covers just installing and running this package.

This package installs the import-lint CLI. It's a thin launcher that execs a prebuilt native binary for your platform (installed automatically via optionalDependencies — no compilation, no postinstall download scripts).

Install

npm install -D @import-lint/cli

The package is named @import-lint/cli, but the installed command is still import-lint (see Quickstart below).

Quickstart

# Scaffold a .importlintrc.jsonc.
npx import-lint init

# Lint the current directory (or your config's `include` roots).
npx import-lint

# ESLint-compatible JSON output, for CI tooling.
npx import-lint --format json

With no config file, ImportLint lints . with the package-access rule at error severity and defaults matching eslint-plugin-import-access.

Use in CI

Exit code 1 on any error-severity diagnostic fails the build on violations; --format github produces inline PR annotations on GitHub Actions:

npx import-lint --format github

See Using in CI in the main repository README for a full workflow example — also see there for the full CLI reference, config file format, output formats, watch mode, and the migration guide from eslint-plugin-import-access.

Editor integration

The ImportLint VS Code extension shows violations as you type, on top of this package's binary — no separate install needed. The binary this package installs also includes import-lint lsp, for wiring up any other LSP-capable editor. See Editor integration in the main repository README for setup details.

Supported platforms

darwin-arm64, darwin-x64, linux-x64-gnu, linux-x64-musl, linux-arm64-gnu, win32-x64. On an unsupported platform (or with --omit=optional installs), the CLI fails at run time with an actionable error rather than breaking npm install for your whole project — see cargo install import-lint or GitHub Releases as fallbacks.

License

MIT