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

@agent-ix/ts-plugin-kit

v0.1.1

Published

Framework-agnostic plugin/marketplace toolkit: typed git/npm sources, ref/sha pinning, install registry, and default-set reconciliation.

Readme

ts-plugin-kit

Framework-agnostic plugin/marketplace toolkit: typed git/npm sources, ref/sha pinning, install registry, and default-set reconciliation. Zero runtime dependencies.

It is the install mechanism shared by Agent-IX CLIs and any other host (the ix CLI, quoin, a future desktop app). It knows nothing about oclif or any particular plugin payload — a host supplies a readName callback and decides what to do with the resolved files.

Usage

import {
  reconcile,
  validateMarketplaceManifest,
} from "@agent-ix/ts-plugin-kit";

// host parses YAML/JSON itself, then validates the object
const manifest = validateMarketplaceManifest(parsedYaml);

const result = reconcile(manifest, {
  mode: "lazy", // install only what's missing/repinned; zero git when settled
  cacheRoot: "~/.cache/ix/ts-plugin-kit",
  targetRoot: "~/.ix/filament/modules", // <name>/ materialized here
  registryPath: "~/.ix/filament/registry.json",
  readName: (dir) => /* derive a name from the resolved content */ "...",
});
// result.{installed, unchanged, updated, skipped}

A manifest entry's source is one of:

| type | fetches | | ------------- | ---------------------------------------------------- | | github | owner/repo at a ref/sha | | git-subdir | one sparse-checked-out subdir of a repo at a pin | | git | any git URL at a ref/sha | | path | a local directory (dev) | | url / npm | reserved — resolution not yet implemented |

All operations are synchronous (git is the only side effect) and pins are recorded as resolved commit shas, so a settled lazy reconcile performs no git at all.

Included:

  • ✅ CI via agent-ix/nodejs-actions
  • 📦 Local Development via PNPM + Corepack
  • 🧪 Jest for unit testing (supports coverage, JSON output)
  • 💃 Prettier and ESLint for code quality
  • 🏷 Tag-triggered release workflow with registry support
  • 🔖 Automatic versioning based on Git tags

🚀 Getting Started

This project uses pnpm with Corepack for local development.

Prerequisites

  • Node.js 20+
  • Corepack enabled (corepack enable)

Setup

# Install dependencies (uses pnpm version from package.json)
pnpm install

# Build the project
pnpm run build

# Run tests
pnpm run test

📜 Scripts

All development commands are defined in package.json scripts. Run pnpm run help or pnpm run to see the full list.

Core Development

| Command | Description | | ----------------- | --------------------------------------- | | pnpm run build | Compile TypeScript | | pnpm test | Run tests | | pnpm run lint | Run ESLint | | pnpm run format | Run Prettier | | pnpm run clean | Remove build artifacts and node_modules |

Package Management

| Command | Description | | ------------------------------ | ---------------------------------------- | | pnpm run pkg:add <pkg> | Add dependency | | pnpm run pkg:add-dev <pkg> | Add dev dependency | | pnpm run pkg:update | Update dependencies | | pnpm run pkg:use-local <pkg> | Link local package via @agent-ix/js-deps |

Publishing & Docker

| Command | Description | | ------------------------ | --------------------------------------------- | | pnpm run publish | Publish to GitHub Packages (upstream) | | pnpm run publish:local | Publish to local npm.ix registry (via Docker) | | pnpm run docker:build | Build release Docker image |


🛠 Makefile

A Makefile is provided for backwards compatibility. It delegates all commands to the equivalent pnpm run scripts.

make build          # -> pnpm run build
make test           # -> pnpm run test
make local-publish  # -> pnpm run publish:local