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

@brutalway/alint-config

v0.2.0

Published

alint rules for a repository: category folders hold only their kind, every dependency is pinned (only devDependencies for a published library), doc links and anchors resolve.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

elnopelnop

Keywords

alintrepositorylint

Readme

@brutalway/alint-config

alint rules for a repository:

| Rule | Checks | | --------------------------- | -------------------------------------------------------------------------------------------- | | doc-links-resolve | every file link in README.md and docs/**/*.md points to a file that exists | | doc-fragments-resolve | every anchor in those links matches a heading | | styles-only-css | a styles/ folder only holds .css files | | types-only-types-files | a types/ folder only holds XTypes.ts files | | configs-only-config-files | a configs/ folder only holds XConfig.ts files and their tests | | exact-dependency-versions | every dependencies and devDependencies entry of every package.json is an exact version |

npm install --save-dev @brutalway/alint-config @asamarts/alint

.alint.yml:

version: 1
extends:
  - ./node_modules/@brutalway/alint-config/base.yml
rules:
  - id: doc-paths-resolve
    kind: markdown_paths_resolve
    paths: ['README.md', 'docs/**/*.md']
    prefixes: ['src/', 'docs/']
    level: error

alint only follows a local extends that stays inside the linted tree, so the path goes through node_modules. markdown_paths_resolve stays in your file because its prefixes depend on your folders. alint downloads its binary in a postinstall script, which npm 11 runs only once you approve it (allowScripts in package.json).

Library

A published package states its runtime dependencies and peerDependencies as ranges, so the projects that install it can share one copy. library.yml runs the same rules as base.yml, except that exact-dependency-versions only checks devDependencies:

version: 1
extends:
  - ./node_modules/@brutalway/alint-config/library.yml