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

@kingslanding/cli

v0.2.0

Published

Deploy static sites to King's Landing from any terminal or CI/CD pipeline

Downloads

29

Readme

kl — King's Landing CLI

Deploy static sites to King's Landing from any terminal or CI/CD pipeline.

Install

npm install -g @kingslanding/cli

Or run without installing:

npx @kingslanding/cli deploy ./dist

Or with Docker (no Node.js required):

docker run --rm -v $(pwd):/app -w /app ghcr.io/boxshopio/kl deploy ./dist

Requirements: Node.js >= 18 (npm install), or Docker.

Quick start

# Authenticate
kl login

# Initialize a project config
kl init

# Deploy
kl deploy ./dist

Commands

| Command | Description | |---------|-------------| | kl login | Authenticate via browser | | kl logout | Clear credentials | | kl init | Create kl.json project config | | kl deploy [dir] | Deploy a directory (default: .) | | kl projects | List your projects | | kl whoami | Show current user | | kl deploy-key create | Generate a deploy key for CI/CD | | kl deploy-key status | Check if a deploy key exists | | kl deploy-key revoke | Revoke a deploy key |

Deploy

# Deploy current directory
kl deploy

# Deploy a specific directory
kl deploy ./dist

# Deploy with a project name (skips kl.json)
kl deploy ./dist --project my-site

# Auto-create project if it doesn't exist (for CI)
kl deploy ./dist --project my-site --create

# Detailed output
kl deploy ./dist --verbose

Project config

Run kl init to create a kl.json in your project root:

{
  "project": "my-site",
  "directory": "dist",
  "team": null
}

| Field | Description | Default | |-------|-------------|---------| | project | Project name on King's Landing | required | | directory | Directory to deploy | . | | team | Team slug (for team-owned projects) | null |

CI/CD

GitHub Actions

name: Deploy
on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npx @kingslanding/cli deploy ./dist --project my-site --create
        env:
          KL_DEPLOY_KEY: ${{ secrets.KL_DEPLOY_KEY }}

Generate a deploy key

kl deploy-key create --project my-site

The key is shown once. Add it as KL_DEPLOY_KEY in your CI secrets.

Any CI provider

The CLI detects KL_DEPLOY_KEY automatically. No kl login needed.

export KL_DEPLOY_KEY=kl_your_key_here
npx @kingslanding/cli deploy ./dist --project my-site --create

File filtering

Create a .klignore file (gitignore syntax) to control which files are deployed:

node_modules
.git
.env*
.DS_Store

If no .klignore exists, these defaults apply automatically.

Docker usage

For environments without Node.js:

# Deploy
docker run --rm -v $(pwd):/app -w /app ghcr.io/boxshopio/kl deploy ./dist --project my-site --create

# With deploy key
docker run --rm -e KL_DEPLOY_KEY=$KL_DEPLOY_KEY -v $(pwd):/app -w /app ghcr.io/boxshopio/kl deploy ./dist

# Shell alias for convenience
alias kl='docker run --rm -e KL_DEPLOY_KEY -v $(pwd):/app -w /app ghcr.io/boxshopio/kl'
kl deploy ./dist

License

Proprietary. See kingslanding.io for terms.