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

@folotoy/folotoy-openclaw-plugin

v0.9.1

Published

Interactive installer + preset CLI for the FoloToy OpenClaw plugin.

Vulnerabilities

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

Links

Git

Maintainers

lewangxlewangxfolotoy-testfolotoy-test

Keywords

folotoyopenclawinstaller

Readme

@folotoy/folotoy-openclaw-plugin

Interactive installer for @folotoy/folotoy-openclaw-core — generates a pairing QR code, writes the OpenClaw config, restarts the gateway.

npx -y @folotoy/folotoy-openclaw-plugin install [--preset <name>]

Why a separate package

OpenClaw's plugin security scanner (2026.4.x+) rejects packages that contain child_process execution or process.env access combined with fetch() — patterns that any interactive installer legitimately needs. Splitting the installer out keeps the runtime channel package (@folotoy/folotoy-openclaw-core) clean and scanner-passing, while this CLI package is only ever fetched via npx (never via openclaw plugins install).

The installer's installPlugin() step internally runs openclaw plugins install @folotoy/folotoy-openclaw-core@<version> to register the runtime channel plugin.

Presets

Use --preset <name> to bake customer-specific defaults into channels.folotoy.* after pairing. Currently shipped:

| Preset | Effect | |--------|--------| | single-soothing | Sets soothing_loop_enabled = false so only the initial order=1 soothing reply is sent; no further soothing replies are emitted while waiting for the LLM. |

Preset JSON files live in src/presets/. Whitelist is restricted to soothing_loop_enabled (boolean only) — unknown keys cause a fail-fast exit before the QR pairing step.

Pairing API

The installer talks to pair.folotoy.cn to create a pairing session and poll for completion. Override the base URL with PAIR_API_BASE for local testing:

PAIR_API_BASE=http://localhost:18888 node bin/folotoy.mjs install

Development

npm install              # at the repo root
npm test                 # runs both runtime + installer tests
cd installer && npx tsc  # builds installer/dist/

The installer's runtime version is read from its own package.json version field; the runtime plugin npm name is read from package.json folotoy.runtimePackage. Both packages release in lockstep with matching versions.

License

MIT