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

@relkit/tools

v0.7.6

Published

RELKIT tool authoring API; prefer @relkit/app/tools in applications.

Readme

@relkit/tools

Tools are constrained, handler-free views of functions. They inherit the target function's input, output, and declared errors and add only approval and side-effect metadata. Prefer function.asTool when the tool belongs with its function; defineTool is useful when metadata lives in another module.

import lookupOrder from "./lookup-order.function";

const lookup = lookupOrder.asTool({
  description: "Read one order by ID",
  sideEffect: "read",
  approval: "never",
  timeoutMs: 2_000,
});

export default lookup;

Invoke a tool directly with await lookup.invoke(input). Input validation runs before approval, required approval fails closed without a resolver, and the target still enters the common function engine with source tool.

The package also exposes Effect operations. defineToolEffect constructs the descriptor in the typed error channel, and invokeToolEffect obtains its engine from ToolEngineService. This lets tests supply a deterministic engine Layer.

Call defineToolEffect(options) to construct a descriptor. For invocation, provide ToolEngineLive(engine) to invokeToolEffect({ tools, toolId, arguments }) and run the resulting Effect with your application runtime.

Tool operations emit tools.* spans and fixed-label operation, failure, and duration metrics. ToolTelemetry can be supplied in a Layer when an application needs a custom observer.