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

@llanite/cli

v0.2.0

Published

Llanite CLI for installing, running, and customizing local AI stack profiles.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

lachlanforganlachlanforgan

Keywords

Readme

Llanite CLI

Llanite is a CLI-first tool for installing, running, and customizing local AI stack profiles.

This repository currently contains Part 1 of the MVP: the CLI and project foundation.

Development

npm install
npm run build
node dist/index.js --version
node dist/index.js --help
node dist/index.js config paths
node dist/index.js doctor
node dist/index.js doctor local-coder
node dist/index.js fetch
node dist/index.js catalog
node dist/index.js search coder
node dist/index.js inspect local-coder
node dist/index.js stacks
node dist/index.js stacks local-coder

For local development:

npm run dev -- doctor

The published package will expose both commands:

llanite --version
lla --version

Local State

Llanite resolves local state from LLANITE_HOME when set, otherwise it uses:

~/.llanite

Inspect resolved paths with:

llanite config paths
lla config paths

Registry

The MVP currently ships with a bundled sample registry. Fetch validates that registry and caches it locally:

llanite fetch
llanite stacks
llanite stacks local-coder
llanite catalog
llanite catalog --type model
llanite search coder
llanite inspect local-coder
llanite inspect local-coder --json
llanite doctor
llanite doctor local-coder
llanite doctor local-coder --json

For local registry development, override the source:

LLANITE_REGISTRY_SOURCE=/path/to/registry llanite fetch

Renaming Product Terminology

Most product and command terminology is centralized in src/core/identity.ts. To rename the active product terminology across source, tests, package metadata, README, and registry files, use:

npm run rename:product -- --product "Stackpack" --command stackpack --short spk --dry-run
npm run rename:product -- --product "Stackpack" --command stackpack --short spk

The script derives defaults for package scope, local home directory, env var prefix, and bundled agent id. Override them when needed:

npm run rename:product -- --product "Stackpack" --command stackpack --short spk --scope @stackpack --env-prefix STACKPACK --home-dir .stackpack --agent-id stackpack-agent