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

@sstar/boardpilot

v0.1.0

Published

BoardPilot V1 control plane for embedded AI workflows

Vulnerabilities

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

Links

Maintainers

ekko.baoekko.bao

Keywords

Readme

@boardpilot/cli

@boardpilot/cli provides the boardpilot command for starting the Core router, starting the Edge runtime, managing local agent plugins, and checking CrossNet configuration.

Commands

boardpilot core [--init] [--weblink] [--message-channel mqtt|gerrit|ssweb] [--config <path>] [--force] [--non-interactive]
boardpilot edge [--init] [--config <path>] [--weblink-core ws://<core-ip>:7780/edge] [--crossnet-core <core-nodeId>] [--proxy http://<proxy-host>:<port>] [--force] [--non-interactive]
boardpilot core [--weblink] [--message-channel mqtt|gerrit|ssweb] [--config <path>] [--port 7780]
boardpilot edge [--config <path>] [--core ws://<linux-ip>:7780/edge] [--proxy http://<proxy-host>:<port>]
boardpilot edge [--board-ip <ip>] [--com COM4] [--target <name>]
boardpilot crossnet pair-edge --pair-code <code> [--config <path>]
boardpilot crossnet check [--role core|edge] [--config <path>] [--probe-gerrit|--probe-ssweb|--probe-ssbuild|--probe-gerrit-artifact|--probe-ftp-download|--probe-tftp-root]
boardpilot plugin status [--codex-only|--claude-only] [--json]
boardpilot plugin install|update|remove [--codex-only|--claude-only] [--dry-run]
boardpilot plugin doctor [--codex-only|--claude-only] [--core http://127.0.0.1:7780]

Core config defaults to ~/.boardpilot/core-config.json. Edge config defaults to ~/.boardpilot/edge-config.json. Current Core and Edge config files are parsed through the shared schemas before startup or CrossNet checks.

Packaging

The package is self-contained after prepack; runtime apps, internal packages, scripts, and the BoardPilot agent plugin are copied into vendor.

npm run prepack --workspace @boardpilot/cli
npm pack --workspace @boardpilot/cli

Use the root package smoke test to verify install, plugin management, Core startup, Edge startup, and uninstall from a clean consumer project:

npm run test:cli:package