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

@amodalai/snapshot-probe

v0.3.96

Published

Smoke-test package for the release-snapshot workflow. No runtime code — exists purely so the snapshot and release workflows have something non-trivial to publish while verifying the pipeline end-to-end.

Downloads

7,047

Readme

@amodalai/snapshot-probe

Release pipeline smoke-test package. Exists purely to exercise the publish workflows end-to-end so we can tell whether a release ran correctly without using a real published package as the canary.

You probably don't want to install this. It exports nothing useful. It's here so that:

  • Every normal monorepo release publishes this package alongside the real ones, proving the fixed-group lockstep and the NPM_TOKEN setup still work.
  • The snapshot release workflow (.github/workflows/release-snapshot.yml) can publish a prerelease of this package from a feat branch and we can check npm view @amodalai/snapshot-probe dist-tags to see whether the snapshot tag made it through.

Why a dedicated probe instead of relying on @amodalai/core

@amodalai/core is a real package consumed by production code. If a release breaks it (either content-wise or pipeline-wise), rolling back requires real thought. snapshot-probe has zero consumers, so a bad release of it can be ignored and the next release fixes it. This keeps the release pipeline's success signal decoupled from the production packages' code quality.

How to use it as a liveness check

import { SNAPSHOT_PROBE } from "@amodalai/snapshot-probe";
console.log(SNAPSHOT_PROBE);
// → "@amodalai/snapshot-probe@release-pipeline-smoke-test"

That's it. The package has no other exports.