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

paperclip-clippy-plugin

v0.1.0

Published

Paperclip plugin that replaces host toasts with a Clippy-style assistant overlay.

Vulnerabilities

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

Links

Git

Maintainers

alvarosanchezalvarosanchez

Keywords

paperclippaperclip-pluginclippytoastnotificationoffice-assistant

Readme

paperclip-clippy-plugin

CI License: Apache-2.0 Paperclip Plugin

Experimental Paperclip plugin that hijacks host toasts and re-renders them as a Clippy-style assistant bubble.

This repo is intentionally hacky. The first goal is to get the joke working from a real Paperclip plugin install, then tune the interception heuristics against the host DOM.

Installation

From a local checkout:

pnpm install
pnpm build
npx paperclipai plugin install --local "$PWD"

This repository is prepared for npm publication as paperclip-clippy-plugin. Once published, the standard install flow will be:

npx paperclipai plugin install paperclip-clippy-plugin

Development

pnpm install
pnpm verify
pnpm verify:manual

Useful scripts:

  • pnpm typecheck
  • pnpm test
  • pnpm build
  • pnpm pack:check
  • pnpm verify
  • pnpm verify:manual

pnpm verify:manual builds the plugin, launches a disposable local Paperclip instance, installs this plugin into it, seeds a dummy company to skip onboarding, and opens Paperclip so you can trigger normal host toasts against a disposable instance.

Manual Verification

  1. Run pnpm verify:manual.
  2. Follow the live checklist printed by the command.
  3. Confirm there is no custom Clippy settings page content or test-trigger UI, and no visible global toolbar button.
  4. Trigger a few normal Paperclip actions that show host toasts.
  5. Confirm the native toast is hidden or flashes only briefly.
  6. Confirm the Clippy bubble appears automatically with the intercepted toast text.
  7. Confirm multiple messages are queued in order.

Optional environment variables:

  • PAPERCLIP_E2E_STATE_DIR: keep the Paperclip state under a repo-relative directory instead of a disposable temp dir.
  • PAPERCLIP_E2E_PORT: preferred HTTP port for the disposable instance.
  • PAPERCLIP_E2E_DB_PORT: preferred embedded Postgres port for the disposable instance.
  • PAPERCLIP_E2E_OPEN_BROWSER=false: skip auto-opening the browser during scripted runs.

Release process

  • CI runs from .github/workflows/ci.yml on pushes to main and on pull requests.
  • npm publishing runs from .github/workflows/release.yml when a GitHub Release is published with a semver tag such as v0.1.0.
  • The release workflow stamps package.json from the release tag, verifies the package, publishes with provenance, and syncs the checked-in version back to the target branch.