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

@kisuke/cli

v1.2.30

Published

Lifecycle-free bootstrapper for the Kisuke CLI runtime

Readme

@kisuke/cli

Lifecycle-free bootstrapper for the Kisuke CLI. Installing this package does not download a runtime, start a daemon, or register a service. The first kisuke invocation verifies and installs the matching signed runtime beneath the flavor-aware Kisuke home directory, then runs it with the original arguments and stdio.

npm install -g @kisuke/cli
kisuke

Runtime files live in ~/.kisuke/runtime for production, ~/.kisuke-staging/runtime for staging, or beneath KISUKE_HOME when set. npm uninstall intentionally leaves shared runtime and user data intact; use kisuke uninstall to remove the runtime while preserving user data.

Supported overrides:

  • KISUKE_HOME: absolute Kisuke home directory.
  • KISUKE_RUNTIME_PATH: absolute path to an already prepared bundle.
  • KISUKE_VERSION: exact runtime version for this invocation.
  • KISUKE_DOWNLOAD_URL: HTTPS origin, or loopback HTTP for tests.
  • KISUKE_NO_PROGRESS=1: disable download progress.
  • KISUKE_LAUNCHER_PATH: installed launcher used for daemon restoration after activation.
  • HTTPS_PROXY, HTTP_PROXY, and NO_PROXY: download proxy configuration.

The package contains no third-party runtime dependencies and no npm lifecycle scripts. Release workflows must replace manifestPublicKeyBase64 in config.json with the base64-encoded trusted RSA public-key PEM used to sign the exact bytes of every manifest.json.

See docs/runtime-installer.md for the full resolution, verification, activation, update, rollback, release, and removal design.

Runtime manager

runtime-manager.mjs is also an executable helper for the bundled CLI and the native installer:

runtime-manager.mjs resolve [--version VERSION]
runtime-manager.mjs launch [--package-version VERSION] [--legacy-root DIR] -- [CLI_ARGS...]
runtime-manager.mjs install [--version VERSION] [--no-activate] [--prune]
runtime-manager.mjs install-launcher [--no-modify-path]
runtime-manager.mjs activate --version VERSION
runtime-manager.mjs prune
runtime-manager.mjs remove

install additionally accepts --manifest, --signature, and --archive for a native stage-zero installer that has already downloaded those files.