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

imprnt-plugin-timemachine

v0.1.0

Published

imprnt plugin: an opt-in local snapshot safety net. Before any mutating tool runs, it snapshots your git working tree (respecting .gitignore) to a side ref, so the agent cannot lose unrecoverable work. Never blocks, local only.

Readme

imprnt-plugin-timemachine

An opt-in local snapshot safety net. Before any mutating tool runs, timemachine snapshots your git working tree to a side ref, so the agent can never lose work git cannot otherwise bring back: an untracked file, an uncommitted change. It is built for sessions you run with --dangerously-skip-permissions, where there is no prompt between the agent and your files.

It never blocks a tool, it never captures anything .gitignore hides, and it never leaves your machine. Recovery is plain git.

What it captures

  • Tracked changes plus untracked-but-not-ignored files. Exactly what git add -A would stage, and nothing more.
  • Not anything in .gitignore (your .env, keys, build output), and not obvious secret shapes (.env, *.pem, *.key, *.p12, *credentials*) even if you forgot to ignore them. A properly ignored secret is structurally impossible to capture.
  • Snapshots are commits under refs/timemachine/, on no branch, never pushed. They stay in your repo's .git, local only. It keeps the most recent 200 and prunes the rest.

Install

Installing this is a conscious decision: it watches every mutating tool and writes snapshots into your repo. Nothing happens until you opt in.

imprnt plugin add timemachine

This copies the plugin into plugins/timemachine/ and wires it. Timemachine is a native Claude Code plugin: its hooks/hooks.json registers timemachine.js --hook as a PreToolUse hook on the mutating tools, and imp passes the folder to every session it launches via --plugin-dir. Nothing is ever written into your Claude settings.

Not using imp? Load it with claude --plugin-dir plugins/timemachine, or point a PreToolUse hook in your own settings.json at node plugins/timemachine/timemachine.js --hook.

Recover

node plugins/timemachine/timemachine.js list                 # snapshots here, newest first
node plugins/timemachine/timemachine.js restore <id> <path>  # bring a file back into the working tree
node plugins/timemachine/timemachine.js show <id>            # what a snapshot holds (git show --stat)
node plugins/timemachine/timemachine.js status               # count, location, last snapshot time
node plugins/timemachine/timemachine.js wipe                 # delete every timemachine snapshot in this repo

Remove

imprnt plugin rm timemachine

Or delete the import line by hand. Add --purge to also delete plugins/timemachine/. The hook lives inside the plugin folder, so removal undoes the wiring. Existing snapshots stay in .git until you wipe them.

Limits

It protects files inside a git repo only, so it pairs with keeping your work in git. It is damage recovery, not security and not an off-machine backup: it does nothing for npm supply-chain risk or anything outside the repo. And it is a snapshot of the pre-tool state, not prevention - the agent still does the thing, you just get to undo it.