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

@protectqa/agent-runner-local

v0.1.0

Published

Local Agent Studio execution plane — vendor keys stay on your machine; ProtectQA is the control plane.

Readme

@protectqa/agent-runner-local

Local execution plane for ProtectQA Agent Studio. API keys and model calls stay on your machine; ProtectQA stores teams, boards, runs, and audit metadata only.

Requirements

  • Node.js 18+
  • A ProtectQA account with Agent Studio enabled
  • Supabase migration 052_agent_studio_autonomous_runs.sql applied on your org

Quick start

1. In the browser

  1. Open Agent Studio → Vendors & Runtime
  2. Click Generate pairing code and copy the code
  3. Create a team and use Launch autonomous team with an objective

2. On your machine

npx @protectqa/agent-runner-local setup
npx @protectqa/agent-runner-local pair
npx @protectqa/agent-runner-local login
npx @protectqa/agent-runner-local add-key openai
npx @protectqa/agent-runner-local start

For a custom API host (self-hosted):

export TCL_API_URL=https://your-api.example.com
npx @protectqa/agent-runner-local pair

3. Auth token (login)

The runner needs a Bearer token to sync JSONL events to the cloud. After signing in to ProtectQA in the browser:

  1. Open DevTools → Application → Local Storage
  2. Find sb-*-auth-token and copy the access_token from the JSON
  3. Run agent-runner-local login and paste it

Or set PROTECTQA_AUTH_TOKEN in your environment.

Commands

| Command | Description | |---------|-------------| | setup | Create ~/.protectqa/agent-runner/ | | pair | Pair with a code from the UI | | login | Save auth token for cloud sync | | add-key <vendor> | Store key in local vault (openai, anthropic, google-gemini, ollama, …) | | register-vendors | Push metadata (not keys) to ProtectQA | | start | Poll and run team jobs (leave running) | | start --once | Process one poll cycle | | status | Show pairing + vault summary | | doctor | Health check | | vendors | List supported providers |

Security

  • Plaintext API keys are never sent to ProtectQA.
  • Vendor registration sends only localKeyRef, label, and a redacted preview.
  • Set PROTECTQA_VAULT_PASSPHRASE to encrypt vault.enc at rest.
  • Revoke a runner from Agent Studio to stop job polling.

Supported vendors (v0.1)

  • openai — Chat Completions API
  • anthropic — Messages API
  • google-gemini — Generate content API
  • ollama / lm-studio — Local HTTP (no key)

Publish (maintainers)

cd packages/agent-runner-local
npm run build
npm publish --access public

License

MIT