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

@forwardimpact/libproto

v0.1.1

Published

Shared protobuf schemas — one editable source for the service contracts every product imports.

Readme

@forwardimpact/libproto

Shared protobuf schemas — one editable source for the service contracts every product imports.

Purpose

libproto carries the canonical .proto files that more than one published package needs to read:

  • proto/tool.proto — tool-call message types (ToolFunction, ToolCall, ToolCallResult, ToolCallMessage, QueryFilter).
  • proto/common.proto — shared message types (Empty, Usage, Message, Choice, Embedding, Embeddings, Conversation). Imports tool.proto and resource.proto.
  • proto/resource.proto — the resource.Identifier referenced by tool calls and conversation messages.

A consumer declares @forwardimpact/libproto as a direct runtime dependency if and only if the consumer itself ships a .proto that imports a shared file. Today that means the four service packages @forwardimpact/svcgraph, @forwardimpact/svcmap, @forwardimpact/svcvector, and @forwardimpact/svcpathway.

How consumers read the schemas

There is no JavaScript export surface — import "@forwardimpact/libproto" yields an empty namespace object on purpose. Consumers reach the schemas via codegen: npx fit-codegen --all scans node_modules/@forwardimpact/*/proto/ for .proto files at install time and treats every directory it finds as an include path.

Files

  • proto/tool.proto
  • proto/common.proto
  • proto/resource.proto
  • src/index.js — empty ESM module so main resolution stays clean across Node and bun.