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

@gitterm/cli

v0.1.0

Published

Complete suit of gitterm tools in one CLI

Readme

@gitterm/cli

Command-line interface for GitTerm to manage your cloud workspaces from the terminal.

Installation

# Run directly with npx
npx @gitterm/cli --help

# Or install globally
npm install -g @gitterm/cli

Quick Start

# 1. Sign in (device-code flow: visit the printed URL and enter the code)
gitterm login

# 2. List your workspaces
gitterm workspace list

# 3. Manage a workspace
gitterm workspace pause <workspaceId>
gitterm workspace restart <workspaceId>

Switching servers (hosted vs self-hosted)

By default the CLI talks to the hosted GitTerm API at https://api.gitterm.dev. If you run your own GitTerm instance, point the CLI at that server instead.

Option 1: Login with --server

# Hosted (default)
gitterm login

# Self-hosted
gitterm login --server https://gitterm.example.com

# Local development
gitterm login --server http://localhost:3000

The chosen URL is saved in ~/.config/gitterm/cli.json and used by later commands.

Option 2: Environment variables

Env vars override the saved config (useful for CI or one-off commands):

export GITTERM_SERVER_URL=https://gitterm.example.com
export GITTERM_API_TOKEN=gt_...   # from Settings → Account → API tokens

gitterm auth status
gitterm workspace list

| Variable | Purpose | | -------------------- | --------------------------------------- | | GITTERM_SERVER_URL | API base URL (no trailing path) | | GITTERM_API_TOKEN | gt_... token; skips device-code login |

Resolution order for each request: explicit options / env vars → saved CLI config → default hosted URL (for login only).

Check which server you are on:

gitterm auth status
# Server: http://localhost:3000

Commands

| Command | Description | | ------------------------------------------------------------------------------------ | --------------------------------- | | gitterm login [--server <url>] | Sign in via device-code flow | | gitterm logout | Clear saved credentials | | gitterm auth status [--json] | Show the logged-in account | | gitterm workspace list [--status <active\|all\|terminated>] [--limit <n>] [--json] | List your workspaces | | gitterm workspace get <workspaceId> [--json] | Show details for a workspace | | gitterm workspace pause <workspaceId> [--json] | Pause a running workspace | | gitterm workspace restart <workspaceId> [--json] | Restart a paused workspace | | gitterm workspace terminate <workspaceId> [--yes] [--json] | Terminate a workspace permanently |

ws works as a shorthand for workspace. All read/write commands accept --json for machine-readable output (errors are emitted as JSON on stderr too), which makes the CLI easy to drive from scripts and editor plugins.

Authentication

gitterm login uses a device-code flow: it prints a verification URL and a short code, you approve the device in your browser, and the CLI receives a user API token.

  • Credentials are stored in ~/.config/gitterm/cli.json
  • The same token works with @gitterm/sdk and other GitTerm integrations
  • Create revocable tokens in the dashboard under Settings → Account → API tokens and pass them via GITTERM_API_TOKEN (with optional GITTERM_SERVER_URL)

Inside a GitTerm workspace

GitTerm injects a separate workspace identity and installs the CLI in supported agent images. When those credentials are present, the CLI switches to a restricted command set:

gitterm workspace info
gitterm ports list
gitterm ports open 3000 --name app
gitterm ports open 8080 --name api --public
gitterm ports visibility 3000 public
gitterm ports close 3000

Ports are private by default: only your signed-in GitTerm browser session can reach the URL. Public ports can be reached by anyone with the URL, which is what APIs and webhooks need.

No account commands are exposed in this mode. The workspace cannot list or operate on other workspaces and cannot create a workspace. The CLI does not fall back to a saved user login when any workspace identity variable is present.

Programmatic use

This CLI is a thin layer over @gitterm/sdk. If you are building an integration, use the SDK directly:

import { createGittermClient } from "@gitterm/sdk";

const client = createGittermClient(); // reads the CLI's saved login
const { workspaces } = await client.workspaces.list();

License

MIT