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

@aidex/tools

v1.0.1

Published

Aidex Tools — a central Tool Registry providing reusable, permission-gated tools for engines.

Readme

@aidex/tools

Installation

pnpm add @aidex/tools
npm install @aidex/tools

A central registry providing reusable tools for engines: register once, discover by id or by required permission, execute by id with permission validation gating every call.

Contents

  • types/Tool{ id, name, description, permissions?, inputSchema?, execute(input): Promise<TResult> }. permissions declares what a caller must have been granted before execute() runs. inputSchema is forward-compatible plumbing for future MCP (Model Context Protocol) compatibility — MCP describes tools by name/description/a JSON-Schema input shape, so carrying an optional JSON-Schema-shaped object today means a future MCP adapter can expose these tools without this package changing. No MCP transport or handshake is implemented — that's genuinely future work, not simulated here.
  • registry/ToolRegistryregister(), has(), get(), list() (discovery: every tool), listByPermission(permission) (discovery: tools requiring a given permission), execute(id, input, grantedPermissions?). Duplicate id registration throws @aidex/core's own DuplicateRegistrationError (reused, not reimplemented).
  • ToolNotFoundError — thrown by execute() for an unregistered id. has()/get() stay plain accessors, matching every other registry in this codebase.
  • ToolPermissionDeniedError — thrown by execute() when grantedPermissions doesn't cover every permission the tool declares as required. Carries missingPermissions — exactly what's absent, not the full required set. The tool's own execute() is never called when this check fails.

Permission validation

execute(id, input, grantedPermissions = []) compares the tool's declared permissions against grantedPermissions (a flat list of permission name strings) before invoking the tool. A tool declaring no permissions runs unconditionally regardless of what's granted.

Dependency direction

@aidex/tools depends on @aidex/core only (DuplicateRegistrationError, reused). No dependency on @aidex/engines, any provider, strategy, plugin, or application code — tools are meant to be reusable by engines, not coupled to any one of them.