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

@coderifts/release-acceptance

v1.0.5

Published

Public 17-control release-acceptance matrix. Uses only npm registry tarballs, git tags, and live docs URLs — no sibling checkouts.

Vulnerabilities

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

Links

Git

Maintainers

zsobpeterzsobpeter

Keywords

coderiftsreleaseacceptanceconformance

Readme

@coderifts/release-acceptance

Public, installable 17-control release-acceptance matrix. The last of them, live-docs-readback, is a live GET of coderifts.com — not the local build.

# REPRODUCIBLE: measures a frozen, digest-identified release-set that ships with this package.
npx @coderifts/[email protected] --release --release-set 2026-09-10b

# …or whichever set this package currently considers current:
npx @coderifts/[email protected] --release --release-set current

Pass the set by name, not by path. A relative --manifest package/fixtures/… resolves against your own working directory, not the installed package's — measured, it fails with ENOENT under npx. --release-set looks the name up inside the package you just installed.

# Still supported, and NOT reproducible: without a set, every package resolves to the registry's
# current latest, so a later publish changes this result retroactively. The run says so.
npx @coderifts/[email protected] --release

Uses only public artifacts: npm registry tarballs (integrity-checked), git ls-remote tags/HEAD, and live https://coderifts.com pages. No sibling checkouts, no working-tree paths.

  • stdout — machine JSON (spec: coderifts-release-acceptance.v1)
  • stderr — human table (control, expected, status, source)
  • exit 0 all PASS · 1 a control FAIL · 2 incomplete (missing control / skip / 0/0) · 3 --release with PENDING remaining

A missing control, a skip, or 0/0 concurrent is never PASS.

JSON names the exact package versions, git tags, gitHead, tarball URL, dist.integrity, sha256, and the live-doc etag / last-modified / body sha256 it checked. Layer names PUBLIC_TARBALL_VS_TAG, TAG_VS_HEAD, RELEASE_CANDIDATE_VS_HEAD are in layers.