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

@openvole/paw-computer

v1.0.0

Published

Desktop automation Paw for OpenVole — mouse, keyboard, and screen control

Readme

@openvole/paw-computer

npm version

Control the desktop like a human — mouse, keyboard, screenshots.

A Tool Paw for OpenVole that provides desktop automation capabilities using native OS APIs via nut-tree/nut-js.

Install

vole paw add @openvole/paw-computer

Configuration

In your vole.json:

{
  "paws": {
    "@openvole/paw-computer": {
      "allow": [
        "computer_screenshot",
        "computer_click",
        "computer_double_click",
        "computer_type",
        "computer_key",
        "computer_mouse_move",
        "computer_scroll",
        "computer_drag",
        "computer_active_window"
      ]
    }
  }
}

Environment Variables

| Variable | Description | Default | |---|---|---| | VOLE_COMPUTER_DELAY_MS | Delay in ms between mouse actions for reliability | 100 |

Platform Requirements

macOS

  • Accessibility permission — required for mouse and keyboard control. Grant it to your terminal app in System Settings > Privacy & Security > Accessibility.
  • Screen Recording permission — required for screenshots. Grant it in System Settings > Privacy & Security > Screen Recording.

Windows

Works out of the box. No additional permissions needed.

Linux

  • X11 is required. Wayland has limited support for screen capture and input simulation.
  • Ensure libxtst-dev and libpng-dev are installed for nut-js native bindings.

Tools

| Tool | Description | |---|---| | computer_screenshot | Capture the screen and return as base64 PNG with active window info | | computer_click | Click at screen coordinates (x, y) with left or right button | | computer_double_click | Double click at screen coordinates | | computer_type | Type text at the current cursor position | | computer_key | Press a key combination (e.g. ctrl+c, cmd+tab, enter) | | computer_mouse_move | Move the mouse cursor to coordinates without clicking | | computer_scroll | Scroll up or down at a screen position | | computer_drag | Drag from one screen position to another | | computer_active_window | Get the title and bounds of the currently active window |

Usage

The typical Brain workflow with paw-computer:

  1. Screenshot — capture the current screen state
  2. Analyze — the Brain (vision-capable model) interprets the screenshot
  3. Act — click, type, or press keys based on what was seen
  4. Verify — take another screenshot to confirm the action worked
User: "Open Safari and go to example.com"

Brain:
  1. computer_screenshot → sees the desktop
  2. computer_click(x=50, y=780) → clicks Safari in the dock
  3. computer_screenshot → sees Safari opened
  4. computer_click(x=400, y=52) → clicks the URL bar
  5. computer_type(text="example.com") → types the URL
  6. computer_key(keys="enter") → presses Enter
  7. computer_screenshot → verifies the page loaded

License

MIT