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

@agenteer/registry

v1.0.0-rc.2

Published

Agenteer registry: publish, install, search, and pin Agenteer-shaped node packages via npm.

Downloads

253

Readme

@agenteer/registry

Publish/install/search helpers for Agenteer node packages. The registry layer wraps npm directly and adds manifest validation, capability-diff prompts, provenance reporting, and framework.lock management.

Install

npm install @agenteer/registry @agenteer/core zod

Requires Node >= 20.

What it does

  • publishNode(opts) — validates framework.json, enforces the package-name convention, and runs npm publish.
  • installNode(opts) — installs a node package into a workflow, validates it, computes the capability diff, records the install in framework.workflow.yaml, and pins the manifest hash in framework.lock.
  • searchNodes(opts) — keyword search over npm with curated-index annotations when available.
  • validateNodePackage(dir) — standalone validator with issue codes like bad_package_name, missing_framework_keyword, id_mismatch, and manifest_load_failed.
  • jsonSchemaToZod(schema) / compileNodeSchemas(manifest) — AJV-backed bridge for published JSON Schema manifests.

Naming convention

Node packages must use the enforced scope/short-name convention:

@<scope>/node-<name>

Example: @agenteer/node-file-read or @acme/node-bug-triage.

Publish flow

import { DefaultNpmRunner, publishNode } from "@agenteer/registry";

const result = await publishNode({
  pkgDir: "./my-node",
  npm: new DefaultNpmRunner(),
  dryRun: true,
});

if (!result.ok) {
  console.error(result.validation.issues);
} else {
  console.log(result.manifest_id, result.manifest_hash);
}

PublishResult reports the validated manifest id, package version, manifest hash, provenance status, and whether the run was a dry-run.

Install flow

import { DefaultNpmRunner, installNode } from "@agenteer/registry";

const result = await installNode({
  spec: "@acme/node-bug-triage",
  workflowDir: "./my-workflow",
  npm: new DefaultNpmRunner(),
  autoApprove: false,
  confirm: async ({ summary_text }) => {
    console.log(summary_text);
    return true;
  },
});

if (!result.ok) {
  console.error(result.reason);
}

A third-party package with dynamic_actions: true ignores autoApprove and requires an explicit confirmation callback response.

License

MIT — see LICENSE.