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

@brainpilot/plugin-sdk

v0.2.2

Published

Stable manifest, Preview RPC, validation, and packaging SDK for BrainPilot plugins

Vulnerabilities

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

Links

Maintainers

gtc233gtc233haoxuanlithucaihaoxuanlithucaifxde42fxde42

Keywords

Readme

@brainpilot/plugin-sdk

Stable Manifest v1, Agent Instructions v1, service contracts and Preview RPC v1 types for BrainPilot plugins. Previewers declare contributes.previewers[].match and communicate with the host using the exported PreviewHostToPluginMessage / PreviewPluginToHostMessage unions.

Node helpers under @brainpilot/plugin-sdk/node validate, scaffold, and pack JSON plugin bundles. Publishable manifests must declare a valid engines.brainpilot SemVer range; generated templates use the current lockstep BrainPilot minor range.

Conformance and compatibility-matrix helpers are exported from @brainpilot/plugin-sdk/testing. The BrainPilot CLI exposes them as brainpilot plugin test; no separate testing npm package is used.

Catalogue and lifecycle

BrainPilot reads the built-in catalogue, <dataDir>/plugins/marketplace.json, and optional HTTPS catalogues declared in <dataDir>/plugins/marketplace-sources.json. Catalogue releases point to an immutable JSON bundle and its SHA-256 digest. Installed state is kept under <dataDir>/plugins/; incompatible plugins remain installed but cannot be enabled. Updates keep one real previous bundle for rollback.

Catalogue entries may also describe provenance without changing Manifest v1: sourceFormat (brainpilot, codex, claude-code, or pi-package), an HTTPS repositoryUrl, license, pinned upstreamRef / upstreamCommit, compact capabilities (skills, mcp, hooks), runtime requirements, and an unsupported list. executesLocalCode lets the details panel warn before a trusted Pi extension or other executable integration is enabled, without adding another badge to compact cards. The separate source field remains the catalogue transport (builtin, local, or https). Older entries default to the BrainPilot source format.

Enabled local Pi packages may declare package.json#pi.extensions. BrainPilot loads only extension files copied into that immutable installed plugin root; host-global Pi extension discovery remains disabled. Extension paths must be relative JavaScript or TypeScript files, take effect in new sessions, and are removed from new sessions when the plugin is disabled. Enabling such a plugin is an explicit trust decision because Pi extensions execute in the agent runtime.