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

@openclawbrain/openclaw

v0.4.48

Published

OpenClawBrain plugin/runtime payload for OpenClaw. Operator CLI and install helpers move to @openclawbrain/cli.

Downloads

2,667

Vulnerabilities

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

Links

Git

Maintainers

jonathangujonathangu

Keywords

openclawbrainopenclawpluginruntimeroute-fnintegration

Readme

@openclawbrain/openclaw

Plugin and runtime payload internals for the current OpenClawBrain selective-intervention lane.

Most operators should start with the openclawbrain front door, not with manual package management:

openclawbrain install --openclaw-home ~/.openclaw
openclaw gateway restart
openclawbrain status --openclaw-home ~/.openclaw --detailed

install is the public front door for the selected home. It writes or repairs the hook for that home and pins the activation root the runtime serves from. status --detailed is the quick verify surface.

When you need durable operator evidence today, run:

openclawbrain proof --openclaw-home ~/.openclaw

This package is still the runtime payload under the hood. If you are explicitly managing the native package layer yourself, use OpenClaw's plugin manager for @openclawbrain/openclaw, then rerun openclawbrain install --openclaw-home ~/.openclaw.

Those surfaces prove install / runtime / reporting truth for one selected home. They are not, by themselves, a broad answer-quality claim.

Public docs should lead with the OpenClawBrain product lane and the openclawbrain install command, not with direct runtime-package management.

What this package contains

  • the OpenClaw plugin manifest
  • the installed extension runtime guard
  • compileRuntimeContext() and related runtime load helpers

If this package is installed before the CLI pins the activation root, the extension fails open and logs BRAIN NOT YET LOADED instead of blocking the agent.

Docs