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

@afps-spec/types

v1.0.0

Published

TypeScript bindings for AFPS 1.3+ contracts — Tool protocol, manifest refs, and the RunEvent wire envelope.

Downloads

945

Readme

@afps-spec/types

TypeScript bindings for AFPS 1.3+ contracts.

This package is the canonical TS projection of the language-agnostic AFPS specification (see afps-spec/spec.md). It declares types only — no runtime behavior — so any AFPS-compliant TypeScript tool, runtime, or runner can depend on it to share vocabulary without coupling to a specific implementation.

What's in

  • Manifest refs (DependencyRef, ToolRef, ProviderRef, SkillRef, JSONSchema) — parallel to the Zod schemas in @afps-spec/schema.
  • Tool protocol (Tool, ToolContext, ToolResult) — the shape every AFPS tool implementation MUST satisfy.
  • Wire envelope (RunEvent) — open event shape flowing from tools to sinks.

What's out

Runtime-internal interfaces (bundle loader APIs, resolver interfaces, sink interfaces, aggregated run state) live in the runtime package that owns the implementation — e.g. @appstrate/afps-runtime. They describe how a specific TypeScript runtime wires itself up internally, not contracts shared across the ecosystem.