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

@reticlehq/init

v3.2.0

Published

Reticle project scaffolder — detects the framework, writes the config, patches the build and registers the MCP server. The build-time half of `reticle init`.

Downloads

2,330

Readme

@reticlehq/init

The project scaffolder behind reticle init. Detects the framework and package manager, writes .reticle.json, patches the build config, generates the connect snippet and the agent rules, and registers the Reticle MCP server with whichever clients are on the machine.

Split out of @reticlehq/server because nothing in here observes a running app: it is a build-time codemod that runs once. Keeping it inside the daemon meant a typo in a generated snippet forced a republish of the MCP server, and every MCP user downloaded a scaffolder they run once or never.

You do not install this directly — @reticlehq/server depends on it and the reticle CLI drives it:

npx @reticlehq/server init

Using it as a library

import { buildNodeIo, runInit, type InitHost } from '@reticlehq/init';

const io = buildNodeIo(process.cwd(), host); // host: version, tracing, telemetry, pairing token
const result = runInit(
  { cwd: process.cwd(), port: undefined, mcp: true, dryRun: false, install: true },
  io,
);

InitHost is the seam: everything the scaffolder cannot know for itself — the release version, a tracing hook, where to report the outcome, the bridge pairing token, the declared install channel — is supplied by the caller. That is what keeps this package free of any dependency on the daemon.

License

FSL-1.1-ALv2 — free for any Permitted Purpose, converts to Apache-2.0 two years after release. See LICENSE.