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

@ivy-apps/deslop

v0.13.0

Published

Static import-graph analyzer for TypeScript. Architecture rules in YAML, enforced on every run.

Readme

Deslop

GitHub Stars Haskell Quality

Static import-graph analyzer for TypeScript. You write architecture rules in YAML; Deslop checks them on every run.

You define your architecture once — what modules may import, what they must import, and what companion files must exist (unit tests, Storybook stories). When a rule breaks, Deslop reports exactly what broke and how to fix it, in plain language that both your team and your AI agents can act on.

No AI and no heuristics: it walks the import graph, so the same code always produces the same result.

Deslop is complementary to ESLint and Biome. Where it does replace something is architecture enforcement — the import-boundary rules and companion-file checks you'd otherwise spread across Dependency Cruiser configs and hand-written ESLint plugins.

Install

npm install --save-dev @ivy-apps/deslop

Or run it without installing:

npx @ivy-apps/deslop check .

Usage

Write your rulebooks as YAML files in deslop/rules/, then run:

| Command | What it does | |---------|--------------| | deslop check <project> | Report all rule violations | | deslop fix <project> | Auto-fix violations where possible | | deslop baseline <project> | Write deslop/baseline.yaml to silence current violations | | deslop explore <project> | Write an interactive module graph to deslop/diagram/index.html, and open it (--ci never opens it) |

Recommended package.json scripts:

{
  "scripts": {
    "deslop": "deslop check .",
    "deslop:fix": "deslop fix . && npm run lint:fix",
    "deslop:baseline": "deslop baseline ."
  }
}

A rule looks like this

id: feature-sliced
name: Feature-Sliced Architecture
rules:
  - id: feature-isolation
    description: Features must not import from other features.
    target: "@/features/**"
    forbids:
      - import: "@/features/**"
    allows:
      - import: "{{TARGET_DIR}}/**" # own feature is always fine
    fix: >-
      Promote shared logic to @/components, @/hooks, @/lib
      or an appropriate shared folder.

Rules can forbid imports (directly or transitively), whitelist exceptions, require imports, and require companion files such as tests or Storybook stories. Patterns support casing variables like {{FileName}} and {{TARGET_DIR}} so a single rule stays relative and reusable.

Requirements

  • Node.js >= 18
  • Prebuilt binaries for darwin-arm64, linux-x64, linux-arm64, and win32-x64.
  • A @/ path alias configured in tsconfig.json, so Deslop can resolve your modules

Deslop is free and open source. No license key, no account required — in CI or anywhere else.

Documentation

License

MIT © Ivy Apps Ltd