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

@lashprotocol/lash

v0.1.1

Published

Tiny Lash-over-MCP convention helpers for TypeScript.

Readme

lash-ts

Tiny TypeScript helpers for the Lash MCP profile.

Lash is not a replacement transport or a new MCP SDK. It is a convention layer for peer agents that already expose and consume MCP tools:

  • every peer exposes its callable surface as MCP tools;
  • peers call each other with normal MCP client APIs;
  • Lash-shaped results travel in CallToolResult.structuredContent;
  • continuations are explicit structured results that tell the caller what to call next;
  • trace and thread keep distributed work and local agent memory aligned.

Install

npm install @lashprotocol/lash

Requires Node 20+. The package is ESM-only.

Example

import {
  callToolResult,
  continuation,
  lashTool,
  result,
  threadSchema,
  type LashThread
} from "@lashprotocol/lash";

const thread: LashThread = {
  id: "review/agent-runtime",
  resume: "resume_or_create",
  summary: "Review an agent runtime change.",
  turn: 1
};

export const reviewTool = lashTool({
  name: "review_segment",
  description: "Review one assigned code segment.",
  properties: {
    thread: threadSchema(),
    segment_id: { type: "string" }
  },
  required: ["thread", "segment_id"],
  trace: "trace-review-001",
  allowedCallers: ["orch"]
});

export function reviewSegment(args: { thread: LashThread; context?: string }) {
  if (!args.context) {
    return callToolResult(
      continuation("review_segment", {
        from: "worker-1",
        trace: "trace-review-001",
        thread: args.thread,
        paramsHint: { needs: ["local evidence"] }
      })
    );
  }

  return callToolResult(
    result(
      { findings: [], confidence: 0.91 },
      { from: "worker-1", trace: "trace-review-001", thread: args.thread }
    )
  );
}

API

  • threadSchema() returns the JSON Schema for Lash thread metadata.
  • lashTool(options) creates MCP tool metadata with Lash _meta and output schema.
  • result(value, options) creates a structured result envelope.
  • continuation(method, options) creates a structured continuation envelope.
  • stream(partials, value, options) creates a structured stream envelope.
  • lashError(code, message, options) creates a structured error envelope.
  • callToolResult(envelope) wraps a Lash envelope as an MCP-style CallToolResult.
  • validateThread(value), validateSchema(schema, value), and validateMethodName(name) validate Lash boundaries.
  • withThread(args, thread) adds a thread to tool arguments when one is not already present.

Development

npm install
npm run check
npm run demo

The demo is transport-free and shows the contract. MCP SDKs should own server lifecycle, clients, transports, auth, and model calls.

Boundaries

This package owns tool metadata helpers, the Lash structured output envelope, trace/thread validation, and envelope constructors.

This package does not own MCP transports, server lifecycle, client sessions, authentication, authorization, model calls, durable queues, agent memory, or compaction.