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

@kynver-app/tools-cli

v0.0.6

Published

Kynver Tool Marketplace authoring CLI — scaffold, list, and locally invoke a tool against the same sandbox harness Kynver runs in production.

Readme

@kynver-app/tools-cli (kynver-tool)

Author CLI for the Kynver Tool Marketplace — scaffold a tool project, list its tools, and invoke them locally against the same sandbox harness Kynver runs in production.

Phase-1 alpha. Run npm run build in this package (builds @kynver-app/tool-sdk first for tests). Publish SDK then CLI to npm.

Commands

# Scaffold a new tool project
kynver-tool init my-tool

cd my-tool
npm install

# List the tools your module exports
kynver-tool list

# Run one tool locally — instant feedback, no account, no network
kynver-tool invoke greet --args '{"name":"world"}'

invoke uses the same harness + createGuardedFetch Kynver runs in production. What works here also works once it's deployed.

Flags

| Flag | Meaning | |---|---| | --module <path> | Path to the tool module (default ./tool.ts) | | --args '<json>' | JSON arguments for invoke | | --egress <h1,h2> | Egress allow-list for ctx.fetch (else read from kynver.tool.json) | | --dir <path> | (init) Target directory (default ./<name>) |

From inside this monorepo

npm run marketplace:cli -- init my-tool
npm run marketplace:cli -- list --module ./tool.ts
npm run marketplace:cli -- invoke greet --args '{"name":"world"}'

See the Tool Marketplace map.