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

@intempt-technologies/cli

v0.12.1

Published

Schema-driven typed SDK wrapper generator for Intempt

Readme

@intempt-technologies/cli

CLI for Intempt — AI-assisted analytics instrumentation (tracking plans + typed SDK wrappers for 15 platforms), plus a full platform-operations command surface over Intempt's real API.

Install

npm install -g @intempt-technologies/cli

Or run without installing:

npx @intempt-technologies/cli <command>

Requires Node.js >= 18.

One-line install

⚠️ Not live yet — intempt.com/api/cli must serve scripts/install.sh and scripts/install.ps1 before these work. Both scripts are in this package; use the npm install above until the endpoint is wired up.

curl -fsSL https://intempt.com/api/cli | bash        # macOS and Linux
irm https://intempt.com/api/cli/ps1 | iex            # Windows

Either one installs into ~/.intempt with npm underneath and links intempt into ~/.local/bin. INTEMPT_VERSION, INTEMPT_HOME and INTEMPT_BIN_DIR override the version, the install root and the link directory.

They install a second copy, independent of any npm install -g. If you already have one, the copy that runs is whichever directory comes first on your PATH — the scripts warn when they find one.

Run intempt with no arguments for the welcome screen, intempt --help for every command.

From Claude Code

Install the Intempt plugin instead — it installs this CLI, registers the MCP server, and runs a guided setup skill in one step:

/plugin marketplace add intempt/intempt-claude-plugin
/plugin install intempt@intempt-plugins

Then say "run intempt setup".

Authentication

intempt login

Opens a browser (device-code flow, no passwords in chat/terminal). Session is stored at ~/.intempt/auth.json (mode 0600, encrypted), shared with @intempt-technologies/mcp — one login covers both. The key that encrypts it is kept in your OS keychain: the macOS Keychain, the Windows Credential Manager, or the Secret Service on Linux. On a machine without one, such as most servers and containers, the key is kept in ~/.intempt/auth.key instead, and INTEMPT_AUTH_KEY_STORE=file keeps it there always; anyone who can read both files can read the session.

If your account belongs to more than one org/project, intempt login can't guess which one you mean and leaves it unset. Resolve it with:

intempt use --org your-org --project your-project   # or omit both flags for an interactive picker

INTEMPT_ORG/INTEMPT_PROJECT env vars always take precedence over the stored default, for CI/automation.

Commands

Analytics instrumentation

| Command | What it does | |---------|---------------| | intempt init | Interactive wizard — AI codebase scan, guided, or empty tracking plan (intempt.yaml) | | intempt generate | Generate a typed SDK wrapper or REST client from intempt.yaml | | intempt add <event> | Add an event to intempt.yaml interactively | | intempt remove <event> | Remove an event from intempt.yaml | | intempt validate | Validate intempt.yaml | | intempt status [--ci] [--json] [--warn-only] | Check instrumentation coverage | | intempt push | Sync schema to the Intempt console (backend endpoint not live yet) |

Auth

| Command | What it does | |---------|---------------| | intempt login | Authenticate (device-code OAuth, opens a browser) | | intempt logout | Clear stored credentials | | intempt whoami [--json] | Show current user, the active org/project, orgs, and projects | | intempt orgs [--json] | List the orgs you belong to, with your role | | intempt projects [--org NAME] [--json] | List the projects of one org, or of every org | | intempt use [--org NAME] [--project NAME] | Set the default org/project (interactive picker if flags omitted) |

Platform operations (registry-backed, 202 entries across 13 domains)

| Command | What it does | |---------|---------------| | intempt registry list [--json] | List every available command, grouped by domain | | intempt registry describe <tool> [--json] | Show one command's arguments | | intempt <domain> <action> [--flags] [--json] | Call a command directly, e.g. intempt users get_user_overview --email [email protected]. In a terminal the answer is laid out for reading; --json, or piping the output, gives JSON; --output table prints a list as columns and --limit/--offset print part of it | | intempt <domain> --help | List one domain's commands; intempt <domain> <action> --help shows one command's arguments |

Email/name arguments for users/accounts commands resolve to an internal ID automatically — you never need internal IDs.

Content generation (via Blu Chat)

| Command | What it does | |---------|---------------| | intempt content generate-email "<prompt>" [--format html\|plain] | Generate an email | | intempt content generate-sms "<prompt>" | Generate an SMS message | | intempt content generate-push "<prompt>" | Generate a push notification | | intempt content generate-landing-page "<prompt>" | Generate landing page HTML | | intempt content generate-slack "<prompt>" | Generate a Slack message | | intempt content generate-text "<prompt>" | Generate generic text/copy | | intempt content generate-image "<prompt>" | Generate an image |

Each prints the saved record's id, type and title, Blu Chat's summary of what it made, and the generated content; id is null when nothing was saved.

When Blu Chat answers with a plan first, before any content and without a question, the command approves it in the same conversation and prints what that generates, if every step of the plan creates the requested content; any other plan, such as one that changes existing records, is printed unapproved and the command exits 1. When it asks a question instead, also beside a plan, the command prints the question and its options and exits 1, so the next run's prompt can answer it. An approved plan that generates nothing also exits 1, with Blu Chat's words.

intempt gen-email / intempt gen-image are shorthand aliases for the two most common ones.

Development

This package lives in the intempt/cli monorepo, alongside packages/mcp (the MCP server) and packages/commands (the shared API registry both depend on).

bun install
bun run src/index.tsx init      # interactive wizard
bun test                        # test suite
bun run build                   # dist/index.js — Node-runnable, not Bun-only

License

MIT