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 🙏

© 2025 – Pkg Stats / Ryan Hefner

ruins

v0.2.3

Published

> [!IMPORTANT] > This is in beta. Not everything is ironed out and some modules might misbehave

Readme

ruins

[!IMPORTANT] This is in beta. Not everything is ironed out and some modules might misbehave

A CLI tool to track tech debt and aid in migration.

Quick start

npm i -D ruins

Run the CLI

npx ruins

Linting (eslint)

If you're using eslint rules to aid in you migration you might have faced the probelm: how to introduce an error level rule that will forbid breaking a certain rule in new code, while not breaking your build step in existing code, which will be migrated progressively?

Ruins allows to collect all current error level via the [eslint] Collect errors CLI command, and then create in a js file a list of ignores via the [eslint] Create ignores command. Those can be imported in your flat eslint.config file, and used at the end

// eslint.config.js
import { ruinsIgnores } from './.ruins/ignores.js';

export default [
    // your existing rules and plugins
    {...}
    ...ruinsIgnores, // spread the ignores ruins generated, at the end
}

This will set the error level to warn instead of error for the files where the new rule has been broken, while keeping it at error for any other file.

UI

A UI dashboard can be lauched from the CLI. It's in a rudimentary state, but gives a nicer idea of what rules have been broken then looking at the json or js files.

TODOs (beta)

Collects TODO comments in the codebase and allows to have them contain structured metadata. An example would be:

// TODO(created=2025-03-26, author= ian): make vergil happy

To enforce the use of this format and the created date, you can use the integrated eslint rule:

// eslint.config.xx
import ruinsIgnores from 'ruins/rule-todo';

export default [
  {...}
  {
    files: ['src/**/*.ts'],
    plugins: { 'eslint-plugin-structured-todo': ruinsIgnores },
    rules: {
      'eslint-plugin-structured-todo/no-unstructured-todo': 'warn',
    },
  },
}

Config (beta)

While ruins works out-of-the-box with no configuration, a growing list of aspects can be configured with a ruins.config.js(or .ts) file in your root directory.

// ruins.config.ts
import type { RuinsConfig } from 'ruins';

const config: RuinsConfig = {
  dir: ".ruins", // directory where files are stored. Not recommended to .gitignore it
  eslint: {
    preferOff: false, // disabled errors will be turned "off" instead of the default "error"
    filenameOnly: boolean; // identify files by filename only, not path. Inaccurate, useful only if making big directory changes
  },
  group: {
    // in the ui, shows these directories, grouping issues in them together
    dirs: ["src/components/", "src/utils", "api/"],
  },
};
export default config

Made with 🍕 in Amsterdam.