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

@zypherhq/backend-doctor

v0.1.0

Published

npm command wrapper for Backend Doctor.

Readme

Backend Doctor npm Wrapper

This package is the npm command wrapper for Backend Doctor.

Expected user command after public npm publication is complete and npm view @zypherhq/backend-doctor version succeeds:

npx -y @zypherhq/backend-doctor@latest .

Supported published binaries:

  • Linux x64: x86_64-unknown-linux-gnu
  • Linux ARM64: aarch64-unknown-linux-gnu
  • macOS Intel: x86_64-apple-darwin
  • macOS Apple Silicon: aarch64-apple-darwin
  • Windows x64: x86_64-pc-windows-msvc

Current local-development behavior:

  • forwards all arguments to a packaged backend-doctor binary when one is included under bin/<platform>/, vendor/<platform>/, or dist/<platform>/;
  • falls back to cargo run -q -p backend-doctor-cli -- <args> from the repository root for local development when a Rust workspace exists;
  • prints a clear bootstrap error when neither a packaged binary nor a local Rust workspace is available.

Package contents are intentionally allowlisted. Release packaging must stage verified platform binaries and adjacent checksum files before npm pack or npm publish. Staged files match:

  • bin/<platform>/backend-doctor or backend-doctor.exe
  • vendor/<platform>/backend-doctor or backend-doctor.exe
  • dist/<platform>/backend-doctor or backend-doctor.exe

Local release dry runs stage platform binaries from dist/backend-doctor-<target>/ into npm/backend-doctor/dist/<target>/. Public npm publishing requires hosted release artifacts, npm credentials, and the same staged tarball verification from npm/backend-doctor, not the repository root.

Release dry-run checks:

scripts/release/build-local-binaries.sh
scripts/release/stage-npm-package-binaries.sh
npm test --prefix npm/backend-doctor
(cd npm/backend-doctor && npm pack --dry-run)