mrkeyoor.comAsk

stripe/stripe-clitested 05 Oct 2026commit 42b9689

stripe-cli review

Stripe CLI fits Stripe-specific webhook debugging and terminal API work on the strength of its documented commands.

  • Install 23 s
  • Build 77 s
98/101passed, run exited non-zero
  • 160 packages
Dev Toolsevaluationupdated 31 Oct 2026
+3stars / 7d

Use Stripe CLI when you need to test Stripe webhooks, inspect API logs, or manage Stripe objects from a terminal. Our run on October 5, 2026, at commit 42b9689 recorded successful install and build steps, followed by a failing test command. That source-checkout result does not establish whether an authenticated Stripe workflow works: we did not test account login, event delivery to a local handler, or live API operations.

Verdict

Stripe CLI fits Stripe-specific webhook debugging and terminal API work on the strength of its documented commands. Our October 5, 2026, sandbox run at commit 42b9689 recorded a successful install and build but a test-command exit of 1. Investigate the named TestLogin failure before accepting that source pin, and test your authenticated workflow separately. The stored parser summaries do not establish that exactly three individual tests failed.

We ran it

Lab card: what happened when we ran stripe-cli
Lab card from our sandbox run
Screenshot of stripe-cli (docs.stripe.com/cli)
docs.stripe.com/cli
Install✓ · 23s160 packages
Build✓ · 77s
Tests✗ · 35s98 passed · 3 failed of 101 (go test)
Repo691 files~151,667 lines of source · 23 MB · 12 CI workflows · Dockerfile

Answers from our run

Does stripe-cli build from source?

Dependencies installed in 23 seconds (160 packages), and the build succeeded in 77 seconds. We cloned commit 42b9689 into a clean Debian container with 3 CPUs and no project-specific setup.

Do stripe-cli's tests pass?

No. The project's own test command finished in 35 seconds and reported 98 passed, 3 failed (go test).

Who should not use stripe-cli?

Developers seeking a general webhook receiver independent of Stripe.

What are the alternatives to stripe-cli?

stripe-mock, Webhook.site. Stripe CLI fits Stripe-specific webhook debugging and terminal API work on the strength of its documented commands.

Setup4/5Using the visible rubric, broad documented installation choices and successful recorded install/build steps support 4 for installation setup. Authentication was not exercised, and the test command exited 1.
Docs4/5Using the visible rubric, the supplied README and architecture guide cover installation, Docker credentials, command help, and command structure. We did not verify every documented workflow.
Community2/5Last push on 2026-10-05, 2,234 stars and 230 open issues and pull requests is a heavy backlog for its size.Editor’s note: The supplied primary extracts do not establish contributor responsiveness, support quality, or adoption, so they cannot support a community rating.
Maturity4/5Latest release v1.53.0 on 2026-09-30, repository created 2019-06-14 and its test suite did not pass in our sandbox (98 of 101 passed).Editor’s note: One recorded source-checkout run and a release extract do not establish sustained operational reliability or compatibility across supported environments.

How we score

Discussed on

  1. hnStripe CLI706 points
  2. hnStripe-cli10 points
  3. hnStripe CLI – A command-line tool for Stripe3 points

Who it’s for

Developers building Stripe webhook handlers who need event triggering, resending, and local listening commands.
Backend engineers who want Stripe API logs and resource operations in their terminal.
Contributors evaluating a source checkout who can investigate the recorded test failure before accepting a pinned build.

Who it’s NOT for

Developers seeking a general webhook receiver independent of Stripe.
Container workflows that require interactive stripe login; the README directs Docker users to --api-key.
Teams requiring a green source-checkout test command before adoption. Our recorded command exited 1, and the supplied log does not explain every failure.

Setup reality

Our sandbox run on October 5, 2026, used commit 42b9689. The harness recorded installation succeeding in 23 seconds, a dependency count of 160, and the build step succeeding in 77 seconds. The test step exited 1 after 35 seconds without timing out.

The configured image was golang:1.24-bookworm, with 3 CPUs and 8 GB RAM. The install tail says go: downloading go1.26.5 (linux/amd64), so the image label does not establish that Go 1.24 executed the build. The build tail contains vet-exit:0; it does not demonstrate that an authenticated CLI workflow ran.

For ordinary installation, the pinned README documents npm with Node.js 18 or newer, native package managers, release archives, and Docker. Choose the route for your environment, then validate authentication and your intended Stripe workflow separately. Those operational checks were outside our recorded run.

Should you use Stripe CLI?

Use Stripe CLI when you need to test Stripe webhooks, inspect API logs, or manage Stripe objects from a terminal. Stripe documents event triggering and resending, API log tailing, and object creation, retrieval, updating, and deletion. Those capabilities make it a candidate for Stripe integration work; our sandbox did not exercise them against an account.

The pinned README describes the checkout we measured. The architecture guide explains that many resource commands are generated from an OpenAPI specification and use generic operation commands. That explains the command structure without proving that every operation works in a particular integration.

What our run established

Our run on October 5, 2026, at commit 42b9689 recorded successful install and build steps, followed by a failing test command. These observations belong to our sandbox, rather than to a fresh execution for this correction.

The harness records each step's outcome, exit code, elapsed time, timeout status, and retained log tail. Installation took 23 seconds and exited 0. The build step took 77 seconds and exited 0. The test command took 35 seconds and exited 1. None of those steps timed out.

The stored parser summaries report 98 passed, 3 failed, and 101 total; the raw record labels the corresponding outcomes as packages. These are stored parser summaries, not verified counts of unique individual tests or exhaustive coverage. We have not reconciled the complete logs, and the retained excerpt must not be summed to produce replacement totals.

The raw test tail names TestLogin and the pkg/login package as failing. It does not supply a cause or identify every failure represented in the stored summary. Successful package lines elsewhere in the excerpt do not cancel that failure. The rpc line says it has no test files; that is not a failed test.

What the environment leaves uncertain

The sandbox configuration specifies 3 CPUs, 8 GB RAM, and golang:1.24-bookworm. However, installation downloaded Go 1.26.5. Treat the container image and the downloaded toolchain as separate facts; this record does not justify describing the result as a verified Go 1.24 build.

We did not test authenticated login, delivery to a local webhook handler, live-mode requests, or command latency against Stripe. A zero exit from the build step establishes that step's recorded outcome, not successful deployment or operation of the CLI. No audit result or scanned-package coverage is supplied, so security scan coverage is unknown.

The testing methodology explains how MrKeyoor presents command outcomes and their limits. It supplies provenance context, not proof that this older run used today's procedure or completed an unrecorded workload.

Docker changes the authentication setup

The pinned README says Docker does not support stripe login and directs users to --api-key. It also documents password-store setup for live-mode requests and permits a per-command API key. Plan credential handling before choosing the container route; our run did not validate either authentication approach.

Native installation has documented routes through npm, Homebrew, Linux package managers, Windows package managers, and release archives. Documentation coverage helps you choose an installation route, but our source-checkout timing is not a measurement of those prebuilt distributions.

Which alternatives fit which task?

stripe-mock is a complement for basic API request sanity checks, not a replacement for testing Stripe integration behavior. Its README describes hardcoded responses and explicitly says it does not reproduce the real API's behavior. Use it to check request URLs and parameter shapes, then test integration changes against Stripe test mode. Do not select it on the assumption that it provides realistic payment state or error responses.

Webhook.site provides a unique URL for receiving and inspecting webhook requests. Choose it when the immediate task is examining incoming HTTP payloads. Its repository distinguishes a self-hostable open-source version from a cloud version with additional features; Custom Actions are absent from the open-source version. It can complement Stripe CLI during debugging, but a request receiver does not replace Stripe resource commands.

How to read the scores

For assessed dimensions, 1 means the supplied evidence shows a substantial obstacle, 2 means substantial manual work or important gaps, 3 means usable with a material qualification, 4 means broad documented support with a stated limitation, and 5 requires direct evidence across the intended workflow with no material observed obstacle. These are editorial judgments, not benchmark results. Unknown dimensions remain unassessed.

Setup ease receives 4 for the documented installation choices and successful recorded install and build steps. This assesses getting the software installed and built; the failing test command and untested authentication remain explicit limits. Documentation receives 4 for installation, credential handling, command help, and architecture coverage, without claiming that we verified every documented workflow. Community and maturity remain unassessed because the supplied extracts do not establish contributor responsiveness, adoption, or sustained operational reliability.

Before accepting commit 42b9689 as a source pin, investigate TestLogin and obtain the complete failing-command output. Before using the CLI for integration work, validate authentication and the specific webhook or API operation you intend to use.

Alternatives

ProjectWhat it isPick it when
stripe-mockA mock HTTP server for basic Stripe API request sanity checks, with hardcoded responses and limited behavior.Use it alongside integration testing to check request URLs and parameter shapes. It does not replace Stripe test mode or realistic payment-flow tests.
Webhook.siteA webhook and HTTP request receiver with a self-hostable open-source version and a cloud service.Choose it to inspect incoming payloads at a generated URL. It can complement Stripe CLI, while Stripe resource operations remain a separate task.

What people are saying

  1. [github-trending] stripe/stripe-cli

Sources

  1. Stripe CLI repository and README
  2. Stripe CLI architecture
  3. Stripe CLI v1.53.0 release
  4. Stripe CLI multi-account project-name issue 2085
  5. Stripe CLI reference

More dev tools reviews