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

@rmartz/repo-hygiene

v10.0.0

Published

Low-cost repo-hygiene CI checks (conflict markers, GitHub Actions SHA pins, docs link integrity, file-size caps, and more), distributed via the rmartz/repo-hygiene-action GitHub Action and kept current by Dependabot.

Readme

@rmartz/repo-hygiene

A suite of low-cost CI checks (conflict markers, GitHub Actions SHA pins, Markdown link integrity, docs frontmatter, file-size caps, and more), packaged so that:

  1. Updates propagate automatically. Consuming repos pin one GitHub Action, rmartz/repo-hygiene-action, by version; Dependabot's github-actions ecosystem opens PRs to bump that pin on its normal schedule.
  2. Adding a check is low-friction for consumers. New checks ship inside this CLI; the Action picks up each release automatically, and consumers pick it up on the next Dependabot bump with no per-repo YAML edits.

Using it in a consuming repo

Check out the repository, then run the Action as a step:

# .github/workflows/repo-hygiene.yml
name: Repo Hygiene
on:
  pull_request:
  push:
    branches: [main]
permissions:
  contents: read
  statuses: write # optional: one commit status per check
jobs:
  hygiene:
    runs-on: ubuntu-latest
    timeout-minutes: 5
    steps:
      - uses: actions/checkout@<sha> # vX.Y.Z
      - uses: rmartz/repo-hygiene-action@<sha> # vX.Y.Z

and a Dependabot entry so the pin stays current:

# .github/dependabot.yml
version: 2
updates:
  - package-ecosystem: github-actions
    directory: /
    schedule:
      interval: weekly

Both files are seeded once by @rmartz/bootstrap (ai-ensure-project-config); after that Dependabot maintains the pin. The @rmartz/repo-hygiene package is public on npmjs, so the install needs no token, packages: read permission, or consumer PAT.

For the full walkthrough — per-check configuration, the file-caps baseline, and how to verify your setup — see the consumer setup & configuration guide. The Action's inputs are documented in its README.

Choosing checks

Omit the checks input and the Action runs the registry's default-on set — and a newly-added default-on check auto-joins on your next Dependabot bump with no edit here. The defaults are strict: every default-on check enforces at error. A repo that intentionally needs laxer rules relaxes them per check in its .repo-hygiene.yml (severity: warn, a laxer option, or enabled: false) rather than trimming the list. To add the opt-in action-pin-tags, name the checks explicitly (this becomes the exact run list, so include the defaults you still want):

- uses: rmartz/repo-hygiene-action@<sha> # vX.Y.Z
  with:
    checks: conflict-markers action-pins package-pins docs-links md-pairing okf okf-index file-caps action-pin-tags
    config: .repo-hygiene.yml

Per-check configuration lives in the consuming repo's .repo-hygiene.yml — see the consumer guide for the full reference.

Checks

conflict-markers, action-pins, action-pin-tags, package-pins, docs-links, md-links, md-pairing, okf (+ okf-fields, okf-index), file-caps — see docs/checks/.

Requirements

  • Node.js >= 20.11
  • pnpm 9 (pinned via packageManager)

Consuming repos need neither — the Action runs the published CLI on a GitHub-hosted runner.

Local development

pnpm install
pnpm run build        # tsup → dist (ESM + d.ts)
pnpm run typecheck
pnpm run lint
pnpm run format:check
pnpm run test         # vitest

# Run the checks against this repo:
node dist/bin/repo-hygiene.js --check

The CLI (repo-hygiene) supports --staged (pre-commit), --check (all tracked files), and --check-diff (files changed vs origin/main); pass check names to restrict the run, --config <path> to point at a config, and --update-baseline to refresh the committed file-caps baseline (legacy mode: baseline).

Releases

Versioned by semantic-release. Every push to main with a releasable conventional commit (feat/fix/…) publishes the @rmartz/repo-hygiene CLI to npmjs (public, via OIDC trusted publishing with provenance), tags v<version>, and cuts a GitHub Release — no release PR and no npm token. Versions up to 7.0.1 were published to GitHub Packages and stay there for existing pins; new versions go to npmjs only. Releases run through the fleet's shared semantic-release-ci workflows, whose required release-check / release-check check renders the release notes with the shared toolchain on every PR, so a broken release setup is caught before merge rather than on the post-merge release run. Consumers get each release through rmartz/repo-hygiene-action, which pins this CLI and re-releases itself when Dependabot bumps it (see #45). The reusable workflow this repo used to ship (.github/workflows/hygiene.yml) has been removed; existing SHA pins to it still resolve but run a frozen CLI 3.0.0.


🤖 Created by Claude Opus 4.8