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

@speakeasy-api/cli

v0.19.4

Published

Speakeasy AI Control Plane CLI

Readme

Speakeasy AI Control Plane CLI

The speakeasy command line interface for the Speakeasy AI Control Plane.

Install

# Homebrew (macOS and Linux)
brew install speakeasy-api/tap/cli

# npm
npm i -g @speakeasy-api/cli

Then authenticate and check your setup:

speakeasy auth
speakeasy whoami

The Homebrew cli formula conflicts with the Speakeasy SDK generator formula (speakeasy-api/tap/speakeasy), because both install a binary named speakeasy. Install one or the other with Homebrew.

Migrating from gram

This CLI was previously named gram. The speakeasy-api/tap/gram Homebrew formula still installs it under the gram name for now, and running it as gram prints a deprecation notice. Switch to the speakeasy command.

You do not need to authenticate again. Profiles now live in $XDG_CONFIG_HOME/speakeasy-ai/profile.json (~/.config/speakeasy-ai/profile.json when XDG_CONFIG_HOME is unset). Until that file exists, the CLI reads your old ~/.gram/profile.json, and the first command that saves a profile copies your profiles to the new file. The old file is left in place. speakeasy auth clear empties both files.

Environment variables and files now use Speakeasy names. The old names keep working, and the CLI prints one deprecation line per run when you still use an old environment variable:

| Old name | New name | | ---------------------------- | ------------------------------------ | | GRAM_API_KEY | SPEAKEASY_AI_API_KEY | | GRAM_API_URL | SPEAKEASY_AI_API_URL | | GRAM_SITE_URL | SPEAKEASY_AI_SITE_URL | | GRAM_ORG | SPEAKEASY_AI_ORG | | GRAM_PROJECT | SPEAKEASY_AI_PROJECT | | GRAM_PROFILE | SPEAKEASY_AI_PROFILE | | GRAM_PROFILE_PATH | SPEAKEASY_AI_PROFILE_PATH | | GRAM_LOG_LEVEL | SPEAKEASY_AI_LOG_LEVEL | | GRAM_LOG_PRETTY | SPEAKEASY_AI_LOG_PRETTY | | GRAM_FUNCTIONS_SDK_VERSION | SPEAKEASY_AI_FUNCTIONS_SDK_VERSION | | gram.deploy.json | speakeasy.deploy.json |

When both names of a variable are set, the SPEAKEASY_AI_* name wins. The CLI never reads plain SPEAKEASY_* names such as SPEAKEASY_API_KEY, which belong to the Speakeasy SDK generator CLI. speakeasy stage and speakeasy push use speakeasy.deploy.json by default, and keep using gram.deploy.json when only that file exists.

Speakeasy Functions

The speakeasy functions commands create, build and deploy Speakeasy Functions projects:

| Command | What it does | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | speakeasy functions init [dir] | Create a project from a built-in template (--template functions or --template mcp). Prompts for missing values on a terminal; --yes uses the defaults. | | speakeasy functions build | Build the project with its own @speakeasy-api/functions (or @gram-ai/functions) package into dist/functions.zip. Needs Node.js 22.18.0 or later. | | speakeasy functions dev | Run the project's dev script. Arguments after -- are passed to it. | | speakeasy functions push | Build, stage and deploy the project. --no-build deploys the existing build. | | speakeasy functions stage | Add a built zip file to the deployment file without deploying, like speakeasy stage function. |

They replace npm create @gram-ai/function and the gf build and gf push commands from @gram-ai/functions, which still work but are deprecated.

The build uses @speakeasy-api/functions when the project has it and falls back to the deprecated @gram-ai/functions, so existing projects build unchanged. The SDK reads speakeasy.config.{ts,mts,js,mjs}, then the deprecated gram.config.*, and builds src/functions.ts, or src/gram.ts when only that file exists.

The project templates live in internal/functions/templates and are embedded in the binary. @gram-ai/create-function copies them from there when it is built, so both scaffolders create the same projects.

To scaffold a project against a local SDK checkout, set SPEAKEASY_AI_FUNCTIONS_SDK_VERSION=file:/path/to/gram/ts-framework/functions when you run speakeasy functions init.

Local Development

  1. Setup environment

    • export SPEAKEASY_AI_API_URL=https://localhost:8080
    • export SPEAKEASY_AI_SITE_URL=https://localhost:5173
    • export SPEAKEASY_AI_ORG=organization-123
    • export SPEAKEASY_AI_PROJECT=default
    • export SPEAKEASY_AI_API_KEY=<API-KEY>
  2. Run desired command

    • cd cli
    • go run main.go status

Testing Speakeasy Functions

  1. Stage zip

    • go run main.go functions stage --slug test-fn --location fixtures/example.zip
    • You never need to do this again as long as you are using the same zip
  2. Push

    • go run main.go push --config speakeasy.deploy.json