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

@lapismd/ai-host

v0.1.0

Published

Standalone ACP process host, WebSocket server, and MCP tool bridge for LapisMD consumers

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

stevejumastevejuma

Keywords

Readme

@lapismd/ai-host

Release npm version

Standalone ACP process host for LapisMD consumers. AI Host owns acpx execution, disposable model discovery, lapis-ai-host serve, the authenticated WebSocket protocol, bounded replay, and the official-SDK MCP stdio shim.

Electron calls the library in-process. Web and Storybook attach with a URL and token after the user starts the CLI. For local browser attach, run pnpm serve:local; the script writes .env with LAPIS_AGENT_RUNTIME_TOKEN when missing and starts serve with that token. Consumer plugins must not depend on this package at runtime.

Install

pnpm add @lapismd/ai-host

Use the root package for in-process hosts, @lapismd/ai-host/client for browser/WebSocket attachment, and @lapismd/ai-host/file-tools for the vault-free file-tool parsing and application helpers.

| Entry point | Purpose | | ----------------------------- | --------------------------------------------------------------------------------------- | | @lapismd/ai-host | ACP executor, server, protocol, replay buffer, token helpers, and tool bridge exports. | | @lapismd/ai-host/client | Browser-side runtime bridge that attaches to a running lapis-ai-host serve process. | | @lapismd/ai-host/file-tools | Algorithm-only file tool schemas, input normalization, diff parsing, and apply helpers. | | lapis-ai-host | CLI launcher for the authenticated local/remote ACP host. | | lapis-mcp-shim | Stable stdio MCP shim launcher used by built consumers. |

Local development

pnpm install --frozen-lockfile
pnpm check
pnpm test
pnpm build

pnpm build writes publishable JavaScript and declarations to dist/. The published package exports built files only; consumer manifests must not depend on local link:, file:, or workspace-only paths.

Release

@lapismd/[email protected] is the manual npm bootstrap release. Prepare and review the tarball with:

pnpm release:plan --registry https://registry.npmjs.org
pnpm packages:pack

The first publish is performed manually from the reviewed tarball. Future versions use Changesets version PRs and npm trusted publishing from .github/workflows/release.yml after the package exists on npm and the npm-production trusted publisher is configured.

Canonical requirements live in spec/src.