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

dsh-isolated-runtime

v0.3.0-alpha.1

Published

Pinned Kubernetes Cell runtime manifests for the DSH multi-tenant platform

Downloads

332

Readme

DSH Isolated Runtime — Cell Alpha

[email protected] delivers the fixed Kubernetes Cell runtime release manifest, CRD, RBAC and platform-mode Operator deployment. Node.js 22+. The runtime images support Linux/amd64 and pin DSH 0.1.5-rc.2.

Existing Kubernetes cluster

Administrators prepare Kubernetes, enforced NetworkPolicy, storage, tenant namespaces, Gateway API, DNS/TLS and private configuration. This package does not create a local cluster or install OIDC. It only prints bundled metadata/YAML; no kubectl, Docker or network access is used by its commands.

npx dsh-isolated-runtime@latest release
npx dsh-isolated-runtime@latest manifests > operator.yaml
# Review namespace/RBAC and replace the example base domain for your environment.
kubectl apply --server-side -f operator.yaml
kubectl -n dsh-system rollout status deployment/cell-operator --timeout=120s

operator.yaml pins the public Operator image by digest. Use the release output's Cell image in the platform's tenant templates; do not substitute mutable tags. The deployment uses --access-mode=platform, with no standalone authorizer or direct Cell HTTPRoute. Applying to an existing installation can change shared cluster resources: review the rendered YAML and kubectl context first.

The paired platform owns OIDC, members, sessions and user protocol access:

npx [email protected] start --config /private/config.json

The platform needs Node.js 24+ and API/Pod network access, usually inside K8s. See the platform setup for tenant templates, networking and private configuration.

Breaking change from 0.2

The standalone Docker/local-cluster launcher is replaced. start, up, stop, uninstall, host archives and macOS installation are not commands in this version. Existing data is not modified by the npm CLI. No automatic migration, historical compatibility, HA or recovery is promised. Historical standalone users must explicitly select [email protected] and its versioned instructions.

Alpha maturity is in the version name; npm uses latest and GitHub uses Release / Latest. The package embeds immutable image identities, the runtime source SHA and SHA-256 of its bundled deployment YAML. --verify-release checks that local binding; it is not a signature or a claim of cluster readiness.