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

agenqa

v1.1.8

Published

AgenQA CLI for running cloud projects

Readme

AgenQA

Run your AgenQA tests from any terminal with a clean, predictable workflow.

Quick Start

  • Install: npm i -g agenqa
  • Import a project: agenqa import --project <projectId> --key-secret <secret>
  • Run tests: agenqa run-project --project <projectId>

Project Management

Import a Project (Step by Step)

  1. Open AgenQA, go to Project settings → Cloud Sync, and copy:
  • Project ID
  • Key Secret Only the project owner can view and create key secrets.
  1. In your terminal, run:
agenqa import --project <projectId> --key-secret <secret>
  1. Confirm that you trust the source.
  2. Choose whether to enable local cache on this machine (required for cloud cache).
  3. If local cache is enabled, choose whether to enable cloud cache (see the warning below).
  4. You’ll see a sync summary once the import completes.

You’re done — the project is now ready to run.

Import Without Prompts (CI/Pipeline)

Skip the yes/no questions by providing explicit answers:

agenqa import --project <projectId> --key-secret <secret> --trust yes --cache-local yes --cache-cloud no

Accepted values are yes or no. Cloud cache requires local cache, so use --cache-local yes when --cache-cloud yes.

List Stored Projects

agenqa list

Displays imported projects with base URL, cache status, and import time.

Remove a Project

agenqa remove-project --project <projectId>

Removes the local config and synced files for the project. This does not delete the cloud project.

Run Tests

agenqa run-project --project <projectId>
agenqa run-folder --project <projectId> --folder <folderId>
agenqa run-test --project <projectId> --test <testId>

Silent Mode

Suppress non-error logs (still exits non-zero on failures):

agenqa run-project --project <projectId> --silent

Cache Controls

Use cache per run:

agenqa run-project --project <projectId> --cache
agenqa run-project --project <projectId> --no-cache

Or set it once for a project (cloud cache):

agenqa cache --project <projectId> --enable
agenqa cache --project <projectId> --disable

Clear local cache for a project (includes downloaded cloud cache and local-only cache):

agenqa reset-cache --project <projectId>

Warning: cloud cache reuses generated steps from collaborators. Enable it only if you trust the owner and every collaborator. Note: disabling local cache during import also disables cloud cache.

Troubleshooting

  • “Project is not imported”: run the import command again.
  • “Key is invalid or expired”: re-import with a fresh key.