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

temper-domains

v0.7.2

Published

Search domain availability from your terminal

Readme

Install

Choose one:

# Homebrew — macOS or Linux, no separate runtime
brew install jongjinchoi/temper-domains/temper

# npm — Node.js 22.12.0 or newer
npm install -g temper-domains

For a one-off run without a global installation:

npx -y temper-domains search myproject

Standalone release binaries do not require Node.js. Run from source.

Usage

Start with a name:

temper search myproject

Temper checks 30 extensions by default. Use j / k to move, Enter to choose a registrar, i for domain details, and q to quit. Opening a registrar page does not purchase a domain.

temper search myproject --extended          # 60 extensions
temper search myproject --tlds com,io,dev    # choose extensions
temper suggest myproject                   # prefix/suffix ideas
temper search myproject --format json       # scriptable results

Running temper shows common commands. Use temper --help or temper search --help for command options.

Features

  • Extension discovery: browse supported extensions by industry, purpose or region.
  • Name suggestions: try prefixes and suffixes around a candidate.
  • Domain details: inspect registrar, dates and nameservers with temper whois.
  • Watchlist and history: save candidates and revisit earlier searches.
  • JSON output: pipe results into your own tools.
  • Local MCP server: let your AI assistant search domains.
  • Keyboard navigation and themes: work in your terminal.

All commands and shortcuts · Extension filters

Choose from 7 themes with temper init or temper config theme --list. Theme gallery.

Updates

temper update          # Check now; ask before installing
temper update --check  # Check and show guidance without installing

Interactive temper, search, suggest, whois and list also check for updates. Later continues your command and skips the update only for that invocation.

Temper can update verified global npm and Homebrew installations after confirmation. Local, linked and npx-cache installations receive manual guidance. After a successful update, run your command again. Set TEMPER_NO_UPDATE_CHECK=1 to disable automatic checks.

Installation rules and failure behavior

MCP

Install Temper first, then configure your MCP client to start a local stdio server:

command: temper
args: ["mcp"]

This is the command/arguments pair; each client has its own configuration format. It runs the same server as temper mcp.

Codex · Claude Code · Claude Desktop · Cursor · Windsurf · Cline · VS Code

Then ask, for example: “Find domains for myproject.”

Tool inputs, results and limits

Before you rely on a result

  • Availability is a lookup result. It does not guarantee a purchase, price, registration eligibility or trademark clearance. Confirm with the registrar.
  • An unresolved lookup is not an available domain. Timeouts and rate limits can leave partial results. Resume eligible results when the server wait permits.
  • Queries reach external providers. CLI and local MCP run on your machine; providers receive the queried domain and connection metadata. Temper adds no telemetry.
  • The hosted demo runs on a server. Submitted names go to its API for lookup. Local CLI history and watchlist stay on your machine.
  • Update checks contact the release channel. They send no domain names or history, but npm or GitHub can see connection metadata.

Errors, recovery and privacy details

Documentation

  • CLI reference — all options, settings and keyboard shortcuts.
  • Extensions — discovery, filters and selection.
  • Troubleshooting — partial results, limits and recovery.
  • MCP — client setup and tool contracts.

Contributing

Issues and pull requests are welcome. Development and checks.

License

AGPL-3.0-only. Commercial use is allowed; distribution and modified network versions carry source-sharing requirements. License and source details.