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

@hardlydifficult/ci-scripts

v1.0.85

Published

Reusable CI scripts

Readme

@hardlydifficult/ci-scripts

Opinionated CI helpers for this monorepo.

The package is library-first now. Instead of importing a placeholder constant or wiring raw shell scripts together, client code can call the intent directly:

import { ci } from "@hardlydifficult/ci-scripts";

await ci.fix();
ci.requirePinnedDependencies();
ci.requirePackageMetadata();
ci.publish();

Installation

npm install @hardlydifficult/ci-scripts

Defaults

  • Commands auto-detect the workspace root, so they work from any package directory.
  • ci.fix() auto-detects the branch from BRANCH, GITHUB_HEAD_REF, or GITHUB_REF_NAME.
  • Package metadata validation reads the Node baseline from the workspace root package.json.
  • Publishing still defaults to the packages/ directory.

API

import {
  autoCommitFixes,
  assertPackageMetadata,
  assertPinnedDependencies,
  checkPackageMetadata,
  checkPinnedDependencies,
  ci,
  publishPackages,
} from "@hardlydifficult/ci-scripts";

ci.fix()

Auto-commits and pushes generated fixes. Returns a result object with committed, pushed, and rerunRequired.

const result = await ci.fix();

if (result.rerunRequired) {
  process.exitCode = 1;
}

ci.requirePinnedDependencies()

Throws if any package.json under the workspace uses ^ or ~.

ci.requirePinnedDependencies();

ci.requirePackageMetadata()

Throws if a package under packages/ is missing required metadata or has an engines.node mismatch with the workspace baseline.

ci.requirePackageMetadata();

ci.publish()

Publishes changed packages in dependency order and returns a summary of published and skipped packages.

const result = ci.publish();
console.log(result.published.map((pkg) => `${pkg.name}@${pkg.version}`));

CLI

The CLI entry points still exist:

npx auto-commit-fixes
npx check-pinned-deps
npx check-package-metadata
npx monorepo-publish

Auto-commit fixes

auto-commit-fixes now infers the branch automatically. Set BRANCH only when you need to override detection.

| Variable | Required | Description | | ------------------- | -------- | -------------------------------------------------------------- | | BRANCH | No | Explicit branch override | | GITHUB_HEAD_REF | No | Auto-used in PR workflows | | GITHUB_REF_NAME | No | Auto-used in push workflows | | GH_PAT | No | GitHub PAT for pushes that should trigger another workflow run | | GITHUB_REPOSITORY | No | owner/repo, used together with GH_PAT |

Example:

- name: Auto-fix and commit
  run: npx auto-commit-fixes
  env:
    GH_PAT: ${{ secrets.GH_PAT }}

Package metadata validation

Checks:

  • engines.node matches the workspace root baseline
  • required fields: name, version, files, scripts, engines
  • required scripts: build, clean
  • files is not empty

Dependency pinning validation

Recursively checks the workspace root for package.json files while skipping node_modules, dist, and .tmp.

Monorepo publishing

Usage:

npx monorepo-publish [--packages-dir <dir>]

Features:

  • publishes in dependency order
  • transforms internal file: references into published versions
  • bumps patch versions based on npm history for the current major.minor
  • tags each published package in git