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

@aggreggator-labs/config-markdownlint

v0.0.2

Published

Shared markdownlint ruleset for aggreggator-labs repositories - extend it from a repo-local .markdownlint-cli2 config

Vulnerabilities

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

Links

Git

Maintainers

aggreggator-labsaggreggator-labs

Keywords

markdownlintmarkdownlint-cli2config

Readme

@aggreggator-labs/config-markdownlint

The shared markdownlint rules for aggreggator-labs repositories. index.json is the source of truth; the stowed machine config in dotfiles is generated from it and a test keeps the two in sync.

Usage

bun add -d @aggreggator-labs/config-markdownlint markdownlint-cli2

Root .markdownlint-cli2.yaml:

config:
  extends: '@aggreggator-labs/config-markdownlint'
ignores:
  - '**/node_modules/**'

Only the rules are shared; ignores are each repository's own. Editor extension, CLI and CI discover the root file and report the same findings.

Rules

Deviations from the markdownlint defaults; everything else is default:

  • MD009 strict — no trailing spaces, not even in list continuation lines
  • MD013 off — no line-length limit; Prettier owns wrapping
  • MD024 siblings only — duplicate headings flagged only among siblings
  • MD033 off — inline HTML allowed
  • MD040 off — code fences need no language
  • MD041 off — a file need not start with a heading

Publishing

Releases are staged, never pushed live by a machine. A push to main with a new version in package.json runs .github/workflows/publish-npm.yml in the dotfiles repository, which stages the version on npmjs through trusted publishing (GitHub OIDC, no token; no provenance, which npm attaches only for public source repositories). A maintainer then approves it with two-factor authentication — npm stage approve or the package page — and only then is it on the registry. An unchanged version stages nothing and says so. Bump the version here to release; patch bumps (0.0.x) by default.