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

vegapunk

v0.1.6

Published

AI-assisted exploratory testing on top of Playwright

Readme

AI-assisted exploratory testing on top of Playwright. The package is vegapunk.

Charters are ordinary Playwright tests. You write setup and teardown, then call vegapunk.explore() when you want an agent to wander the current page as a persona. Vegapunk reports what it did and any issues.

npm i -D vegapunk

Add two configs next to each other:

  • vegapunk.config.ts — model settings (ai), default timebox, and allowedOrigins
  • playwright.config.tstimeout, use, projects, outputDir, and vegapunk/reporter

Copy examples/todomvc if you want a working lab. Run charters with Playwright. vegapunk.explore() loads vegapunk.config.ts for the model, default timebox, and allowed origins.

ai.apiKey is required. How you load the key is up to you.

import { defineConfig } from 'vegapunk'

export default defineConfig({
  timebox: 10 * 60 * 1000,
  allowedOrigins: ['https://staging.example.com', 'http://localhost:3000'],
  ai: {
    provider: 'openai-compatible',
    model: '~typesafe/jev-latest',
    apiKey: process.env.AI_API_KEY ?? '',
    baseURL: 'https://openrouter.ai/api/v1',
  },
})

timebox in vegapunk.config.ts is how long each agent call may run. Pass timebox on vegapunk.explore() only when that call should differ. timeout is Playwright’s limit for the whole test — set it in playwright.config.ts.

~typesafe/jev-latest (or a pinned slug such as typesafe/jev-1.13) is a decisions model, not a chat model. Keep provider: 'openai-compatible' and baseURL at https://openrouter.ai/api/v1. Vegapunk detects the Jev slug and calls OpenRouter’s Decisions API. Each turn Jev picks a Playwright tool, then picks arguments from the page snapshot. A chat slug such as deepseek/deepseek-v4-flash still works on the same config. visual: true needs a vision-capable chat model — Jev cannot read screenshots.

A persona is who is exploring and how they use the product. vegapunk.explore({ persona }) takes a Persona from createPersona(), not a string.

import { createPersona } from 'vegapunk'

export const Persona = {
  DEFAULT: createPersona({
    id: 'default',
    title: 'Default user',
    profile:
      'Uses the product the way it was designed. Notices when a label, filter, or back button does not match the last action.',
  }),
}
import { test } from '@playwright/test'
import { vegapunk } from 'vegapunk'
import { Persona } from '../personas'

test('a user can add, complete, and filter their items', { tag: '@todos' }, async ({ page }) => {
  await page.goto('./')
  await vegapunk.explore({
    page,
    mission: 'Explore adding, completing, and filtering todos.',
    persona: Persona.DEFAULT,
  })
})
npx playwright test
npx playwright test --ui

The Vegapunk HTML report lands in Playwright’s outputDir under vegapunk-report/ (default test-results/vegapunk-report/index.html). Playwright’s own HTML reporter stays at playwright-report/.

Pass visual: true on vegapunk.explore() when you want a viewport screenshot each turn. It is off by default because it costs tokens and needs a vision-capable model. Override config ai for that call when the default model cannot see images:

await vegapunk.explore({
  page,
  mission: 'Look for layout and contrast issues.',
  persona: Persona.DEFAULT,
  visual: true,
  ai: { model: 'qwen/qwen3.5-27b' },
})

If vegapunk.explore() logs any issue, the Playwright test fails at the end. The Vegapunk HTML report is the handoff (expected / actual, user-level repro steps).

Vegapunk calls your model provider directly. Anthropic, OpenAI, Google, and OpenAI-compatible endpoints (including OpenRouter) work. It does not call Cursor. allowedOrigins in vegapunk.config.ts is required: the model is not called unless the page is on that list. See docs/ai.md.

See docs/ for how it works, charters, personas, config, AI setup, and reports.