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

@albion-labs/cli

v0.1.0

Published

Albion local agent: mirrors your terminals to an Albion canvas. Source-available; only ever mirrors PTY bytes -- never touches your AI login.

Vulnerabilities

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

Links

Git

Maintainers

ipolyphianipolyphian

Keywords

Readme

@albion-labs/cli

The Albion local agent. Runs on your machine, spawns/wraps PTYs (node-pty), and mirrors terminal bytes to the relay over outbound-only WSS. The installed command is albion (albion run / albion share / albion daemon).

Trust stance (D4/D13): source-available from day one; mirrors bytes of your own official CLI sessions; never automates, proxies, or stores your AI-provider login.

npm name (D31, 09/07/26): bare albion and albion-cli are squatted, so the package lives under the claimed org scope — @albion-labs/cli — with bin albion (what users type is unaffected by the registry name). Stage 0: skeleton + the node-pty spawn-helper postinstall guard (see spikes/spike-a/OUTCOME.md).

Environment

| Var | Meaning | Default | |---|---|---| | ALBION_RELAY | Relay WebSocket base (same as --relay) | ws://localhost:3200 | | ALBION_USER | Albion identity (same as --user) | william |

WEPO_RELAY / WEPO_USER are deprecated fallbacks from the pre-rename era: still read for one release (a one-time warning is printed), removed after that. Flags beat env vars; env vars beat defaults.

Publishing

Publish from the repo root with pnpm (never npm publish from this directory — npm does not rewrite the workspace:* dependency on @albion-labs/shared, so the tarball would be uninstallable):

pnpm run release:cli   # publishes @albion-labs/shared, then @albion-labs/cli

pnpm rewrites workspace:* to the real version at pack time and refuses to publish from a dirty tree. On later releases, bump BOTH package versions (or at least every package whose version is already on the registry) before running the script — publishing an already-published version fails and the && chain stops there. Licence remains UNLICENSED (all rights reserved) until William picks the source-available licence text — publishing under it is deliberate: source visible, no licence granted yet.