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

@contractspec/action.validation

v3.7.22

Published

GitHub Action for running ContractSpec CI checks

Readme

@contractspec/action.validation

Website: https://contractspec.io

ContractSpec GitHub Action for CI/CD integration. Wraps the contractspec ci CLI command as a composite action.

What It Does

  • Layer: app (GitHub Action)
  • Consumers: external CI/CD pipelines via lssm/contractspec-action@v1

Usage

name: ContractSpec CI
on: pull_request
jobs:
  contractspec:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: lssm-tech/contractspec/packages/apps/action-validation@main

Inputs

  • checks (default: all) — Checks to run (comma-separated: structure,integrity,deps,doctor,handlers,tests) or "all"
  • skip — Checks to skip (comma-separated)
  • pattern — Glob pattern for spec discovery
  • fail-on-warnings (default: false) — Fail the action on warnings (not just errors)
  • check-handlers (default: false) — Include handler implementation checks
  • check-tests (default: false) — Include test coverage checks
  • upload-sarif (default: true) — Upload SARIF results to GitHub Code Scanning
  • working-directory (default: .) — Working directory for running checks
  • bun-version (default: latest) — Bun version to use
  • mode (default: validate) — Action mode: "validate" (run checks) or "impact" (detect breaking changes)
  • baseline — Git ref to compare against for impact detection (default: base branch from PR context)
  • pr-comment (default: true) — Post impact results as PR comment

Outputs

  • success — Whether all checks passed
  • errors — Number of errors found
  • warnings — Number of warnings found
  • sarif-file — Path to SARIF output file (if uploaded)
  • json-file — Path to JSON output file
  • impact-status — Impact status: "no-impact" | "non-breaking" | "breaking"
  • breaking-count — Number of breaking changes detected
  • non-breaking-count — Number of non-breaking changes detected

Key Files

  • action.yml — GitHub Action definition (composite action)
  • README.md — Usage documentation
  • package.json — Package metadata (private, not published to npm)

Local Commands

  • bun run test — bun test

Recent Updates

  • Replace eslint+prettier by biomejs to optimize speed
  • Stability
  • PublishConfig not supported by bun

Notes

  • All input/output changes must be reflected in both action.yml and README.md.
  • The action is versioned with tags on the repository — breaking input changes require a major version bump.
  • Test locally using act or by referencing the local action: uses: ./packages/apps/action-validation.