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

@ai-coders/installer

v0.4.0

Published

AI Coders product installers.

Downloads

98

Readme

AI Coders Installers

This repository publishes the product-aware @ai-coders/installer CLI while keeping installation code separate from the project templates shared with AI Coders members.

This is proprietary software. The package is published to the public npm registry only so authorized AI Coders users can execute it with npx. Registry availability does not make the project open source or grant reuse, modification, or redistribution rights. See LICENSE.

Use

Create an empty directory and run the installer for the product you want to install:

mkdir my-second-brain
cd my-second-brain
npx --yes @ai-coders/installer@latest second-brain

The same zero-checkout flow works for Severino:

mkdir my-severino
cd my-severino
npx --yes @ai-coders/installer@latest severino

The installer opens Clerk in the browser, verifies product entitlement through the AI Coders API, downloads the authorized immutable release artifact, verifies its SHA-256 checksum, validates its fixed product contract, and copies it into the empty current directory before starting the existing wizard.

Installation requires an active paid subscription plan or standalone product access. A free member can authenticate, but the CLI will not download the product or start the wizard; it opens the AI Coders upgrade page in the browser instead.

Existing product checkout

Run the installer from the root of a supported product repository:

npx --yes @ai-coders/installer@latest second-brain
npx --yes @ai-coders/installer@latest severino

The command always reads the product's contract from fixed files in the current directory — ./invokta.mcp.json for Second Brain, ./package.json for Severino — and does not accept a repository path or an alternate manifest file. The requested product must match the contract before any product installer starts.

Bootstrap only runs when the current directory is exactly empty. A non-empty directory without a valid contract stops before authentication and is never modified. An existing checkout is also authorization-gated: the CLI verifies paid plan or standalone access after validating the contract and before starting the product wizard.

The public OAuth client configuration is bundled with the package, so members do not need to provide Clerk settings. Tokens, signed download URLs, and user credentials remain in memory for the current command and are never logged or persisted. See Installer authentication for the one-time Clerk application setup and security contract.

Develop

npm install
npm run check
npm start -- second-brain

The monorepo currently contains:

  • src/: public CLI, manifest validation, and product dispatch.
  • packages/second-brain/: the private Second Brain installer — node-side pipeline under src/, plus a React + shadcn/Tailwind web UI under ui/ that Vite builds into dist/products/second-brain/ui/.
  • packages/severino/: the private Severino installer — node-side pipeline under src/, plus a React + shadcn/Tailwind web UI under ui/ that Vite builds into dist/products/severino/ui/.
  • packages/installer-ui/: the private, source-only React + shadcn/Tailwind kit shared by both product UIs through a Vite alias. It is not published.
  • docs/adding-product.md: the contract for adding another product installer.

The public tarball contains the root CLI and compiled product implementations; the private workspace packages are not published independently.

Release

Conventional Commit titles drive an automated Release PR with the version and changelog update. Merging that PR publishes @ai-coders/installer through npm trusted publishing without a long-lived npm token. See Releases and npm publishing for the maintainer workflow and one-time registry bootstrap.