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

@kaiba-cloud/cli

v0.1.0

Published

Kaiba CLI — build and deploy your apps from CI or a terminal.

Readme

@kaiba-cloud/cli

Build and deploy your apps to Kaiba from CI or a terminal.

Auth

The CLI authenticates with a scoped deploy token — a kaiba_deploy_ token an org admin mints in the Kaiba console (Environments → Deploy tokens). A deploy token grants only build and/or deploy. It is NOT an org admin key. Store it as a CI secret and pass it as KAIBA_API_TOKEN.

The hub URL defaults to https://cloud.kaiba.ai; override it with KAIBA_HUB_URL or --hub-url.

CLI

kaiba build  --repo <url> --branch <ref> --image <name> [--tag <sha>] [--deploy-service <svc>]
kaiba deploy --service <name> --image <ref>
kaiba status
  • build starts a git-mode build on your cluster and streams status until it succeeds or fails. It builds a pushed git ref. Add --deploy-service to roll the resulting image to that service in one step.
  • deploy retargets one compose service to an image and waits for it to run.
  • status prints each service and its live state.

GitHub Action

jobs:
  ship:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: ai-kaiba/kaiba-action@v1
        with:
          command: build
          repo: ${{ github.server_url }}/${{ github.repository }}
          branch: ${{ github.sha }}
          image: web
          tag: ${{ github.sha }}
          service: web          # chains a deploy after the build
          api-token: ${{ secrets.KAIBA_API_TOKEN }}

Publishing (maintainers)

Published manually — no CI token to rotate. From the repo root:

# 1. bump "version" in packages/kaiba-cli/package.json
# 2. build + publish (publish runs the build via prepublishOnly)
cd packages/kaiba-cli
npm login            # once per machine; prompts for 2FA
npm publish          # access:public is set in package.json; prompts for an OTP

Notes:

  • npm publish uses your interactive npm login, so no long-lived token is stored.
  • npm refuses to republish an existing version — always bump first.
  • The published tarball contains only dist/, action.yml, and this README.

The composite Action runs the compiled CLI, so dist/ must be built. npm publish builds it automatically via prepublishOnly; to build without publishing:

pnpm --filter @kaiba-cloud/cli build