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

openclaw-plugin-plakar

v0.1.7

Published

OpenClaw plugin that snapshots the workspace with Plakar before and after every mutating tool call

Readme

openclaw-plugin-plakar

An OpenClaw plugin that automatically captures a Plakar snapshot of your workspace before and after every filesystem-mutating or shell-executing tool call made by the agent.

No code is snapshotted unless you configure it — the plugin is fully inert until plakar.store is set.


Prerequisites

  1. Node.js ≥ 22
  2. OpenClaw installed and running
  3. Plakar binary in your $PATH

Install Plakar: https://docs.plakar.io/install


Install

openclaw plugins install openclaw-plugin-plakar

Configuration

Set the required store option (all other options have defaults):

# Required: path or URL to your Plakar store
openclaw config set plakar.store /data/plakar-store
# or an S3 store:
openclaw config set plakar.store s3://my-bucket/plakar

# Optional: paths to snapshot (defaults to the agent workspace directory)
openclaw config set plakar.paths '["/workspace", "/etc/myapp"]'

# Optional: snapshot timeout in milliseconds (default: 15000)
openclaw config set plakar.timeout 30000

What gets snapshotted

Snapshots are triggered by tool calls whose names start with:

| Prefix | Examples | |---|---| | fs.write | file writes, file creation | | fs.delete | file deletion | | fs.move | rename, move | | shell.exec | arbitrary shell commands |

Tools that do not trigger snapshots: fs.read, browser.*, canvas.*, memory.*, search.*.


Restore workflows

Once the plugin is installed, the bundled plakar-backup skill teaches the agent how to restore previous snapshots. Just ask:

"Undo the last change" / "Roll back" / "Restore my files"

The agent will list available snapshots and offer to restore the one you choose.

Manual restore commands

# List snapshots
plakar -s <store> ls

# Inspect a snapshot
plakar -s <store> ls <snapshot-id>

# Restore
plakar -s <store> pull <snapshot-id> <path>

Graceful degradation

The plugin is designed to be completely transparent to the agent:

  • If plakar is not in $PATH — logs a warning with install instructions, disables hooks
  • If plakar.store is not configured — logs a warning with config instructions, disables hooks
  • If a snapshot times out or fails — logs a warning, never blocks the tool call

License

MIT