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

scrydon

v0.2.2

Published

The Scrydon developer CLI. Alias for @scrydon/cli, so `npx scrydon` and `bunx scrydon` work.

Readme

scrydon

The unscoped alias for @scrydon/cli, so the short name works:

npx scrydon login https://app.example.com
bunx scrydon login https://app.example.com

That is all this package is. It contains no logic beyond resolving @scrydon/cli's bin and handing over — the implementation, the documentation, and the version that matters all live there.

Which one should I install?

Either. @scrydon/cli is the canonical name and what the docs use; scrydon is here so the obvious command works and so the name cannot be squatted.

Installing both is harmless but pointless: they declare the same scrydon bin, so whichever is linked last wins, and they do the same thing.

scrydon --version reports @scrydon/cli's version

Deliberate. The alias forwards to the real CLI, which reports its own version — the implementation you are actually running. The alias's own version number is packaging metadata and is not what you want in a bug report.