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

@lssm/app.action-pr

v4.0.1

Published

GitHub Action for ContractSpec PR checks

Readme

@lssm/action.pr

Website: https://contractspec.io

GitHub Action that runs ContractSpec validation checks on pull requests. Posts drift reports, validation results, and product views as PR comments.

What It Does

  • Uses @lssm/lib.contracts-spec for contract definitions
  • Uses @lssm/bundle.workspace for workspace analysis
  • Configured via action.yml; no src/ — logic lives in workspace bundle

Usage

name: ContractSpec PR
on: pull_request
jobs:
  contractspec:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: read
      pull-requests: write
    steps:
      - uses: actions/checkout@v6
      - uses: lssm-tech/contractspec/packages/apps/action-pr@main
        with:
          github-packages-token: ${{ secrets.CONTRACTSPEC_PACKAGES_TOKEN }}
          generate-command: 'bun contractspec generate'

For affected private GitHub Packages dependencies, github-packages-token must be a GitHub token that can read the ContractSpec packages granted to the consuming repository, bot, or GitHub App.

Inputs

  • package-manager (default: bun) — Package manager to use (bun|npm|pnpm|yarn)
  • working-directory (default: .) — Working directory for running commands
  • report-mode (default: summary) — Report output mode (summary|comment|both|off)
  • enable-drift (default: true) — Run drift detection after generate
  • fail-on (default: any) — Fail on breaking, drift, any, or never
  • generate-command (default: bun contractspec generate) — Command to regenerate artifacts (required when enable-drift=true)
  • validate-command — Override validation command
  • contracts-dir — Directory containing contract specs
  • contracts-glob — Glob pattern for contract specs
  • token (default: ${{ github.token }}) — GitHub token for PR comments
  • github-packages-token — Optional token used to configure private GitHub Packages auth before dependency installs

Outputs

  • drift-detected — Whether drift was detected
  • breaking-change-detected — Whether breaking changes were detected
  • validation-failed — Whether validation failed

Key Files

  • action.yml — GitHub Action definition
  • fixtures/ — Test report data and validation fixtures
  • .contractspec-ci/contracts.json — CI contract configuration

Local Commands

  • bun run test — bun test

Recent Updates

  • Replace eslint+prettier by biomejs to optimize speed
  • Stability
  • Standardize tool naming to underscore notation

Notes

  • Do not change action.yml inputs/outputs without updating downstream workflow consumers
  • Fixture files are used for CI testing — keep them valid