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

@tepa/types

v0.1.1

Published

Shared TypeScript type definitions for the Tepa agent pipeline

Downloads

259

Readme

@tepa/types

Shared TypeScript interfaces for the Tepa agent pipeline. Zero runtime dependencies — this package contains only type definitions.

Install

npm install @tepa/types

Usage

This package is primarily for custom tool authors who need to implement the ToolDefinition interface without depending on the full Tepa engine:

import type { ToolDefinition } from "@tepa/types";

export const myTool: ToolDefinition = {
  name: "my_tool",
  description: "Does something useful",
  parameters: {
    input: { type: "string", description: "Input value", required: true },
  },
  execute: async ({ input }) => {
    return { result: `processed: ${input}` };
  },
};

Exported Types

Core Pipeline

  • TepaPrompt — Input prompt with goal, context, and expected output
  • TepaConfig — Pipeline configuration (models, limits, logging)
  • TepaResult — Final pipeline output (status, cycles, tokens, logs)
  • Plan, PlanStep — Structured execution plan
  • ExecutionResult — Result from a single execution step
  • EvaluationResult — Evaluator verdict (pass/fail with feedback)

Tools

  • ToolDefinition — Tool contract (name, description, parameters, execute function)
  • ParameterDef — Tool parameter schema
  • ToolRegistry — Interface for tool storage and lookup
  • ToolSchema — Serializable tool schema for LLM context

LLM Provider

  • LLMProvider — Abstract provider interface (complete method)
  • LLMMessage — Chat message (role + content)
  • LLMResponse — Provider response (text, tokens, finish reason, tool use blocks)
  • LLMToolUseBlock — A structured tool call returned by the LLM (id, name, input)
  • LLMRequestOptions — Request options (model, temperature, system prompt, tool schemas)

Events

  • EventName — The 8 event hook points
  • EventCallback — Callback function signature
  • EventRegistration — Callback with continueOnError option
  • EventMap — Map of event names to callback arrays
  • CycleMetadata — Cycle number, total cycles, tokens used

Config

  • ModelConfig — Per-component model assignment
  • LimitsConfig — Max cycles, token budget, timeouts
  • LoggingConfig — Log level and output path
  • DeepPartial<T> — Deep partial utility type