Automic VaultAutomic Vault

brew

Install stripe-mock with Homebrew, zypper

Mock HTTP server that responds like the real Stripe API. Version 0.201.0 via Homebrew; verified 2026-05-28.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install stripe-mock

local Homebrew formula metadata

Linux

openSUSE zypperverified · 92%
sudo zypper install stripe-mock

openSUSE Tumbleweed package metadata · stripe-mock · source: download.opensuse.org

overview

Package summary

Mock HTTP server that responds like the real Stripe API

Commands and aliases

  • stripe-mock

history

Project history and usage

stripe-mock is Stripe's official mock HTTP server for basic sanity checks against the Stripe API shape. It is used in CLI and package-manager contexts as a local binary or service that lets SDKs and integration tests validate request paths and parameters without calling the live Stripe API.

Project history

Stripe's README says the project was first released in 2017 and that its original ambition was broader: returning responses that were realistic as well as type-correct. The same source explains that the scope has since narrowed; stripe-mock is deliberately stateless, hardcoded, and aimed at basic validation rather than full API behavior simulation.

The project is generated from Stripe's OpenAPI specification, which keeps the mock aligned with the latest methods, resources, and fields. That makes it part of Stripe's broader API tooling pipeline rather than a hand-maintained fake service.

Adoption history

Stripe documents use of stripe-mock inside server-side SDK test suites such as stripe-ruby and stripe-go. Package availability in the input shows distribution through Homebrew and zypper, while the official README also documents release downloads, Docker usage, and a Homebrew service.

How it is used

Common usage is to start the `stripe-mock` server locally, then run tests or sample requests against its HTTP and HTTPS ports. The README also documents automatic port selection, Unix socket mode, Docker execution, and Homebrew service management.

Why package nerds care

Package maintainers care about stripe-mock because it turns a remote payments API into a reproducible local fixture for SDK testing. It is intentionally not a full emulator, but its OpenAPI-driven route and schema validation make it useful for packaging, CI, and client-library smoke tests.

Timeline

  • 2017: Stripe first released stripe-mock.
  • Current: Stripe documents a narrowed scope focused on stateless basic sanity checks backed by the Stripe OpenAPI specification.

Related projects

  • Stripe OpenAPI specification, Stripe server-side SDKs such as stripe-ruby and stripe-go, Docker images, Homebrew services, and playback-testing tools such as VCR are documented adjacent points in the official README.

security posture

Risk level: orange

formula declares a Homebrew service.

Risk classifier

orange risk · medium confidence · infrastructure

Why

  • formula declares a Homebrew service

Signals

  • metadata:service

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Formula metadata declares a service or daemon block.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
stripe-mockcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version0.201.0
manager updated2026-05-28
local dataok
upstreamcurrent
latest detectedv0.201.0

https://github.com/stripe/stripe-mock

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:stripe-mock
Version0.201.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/stripe-mock
Homepagehttps://github.com/stripe/stripe-mock
Repositoryhttps://github.com/stripe/stripe-mock
Upstream docshttps://github.com/stripe/stripe-mock#readme
LicenseMIT
Source archivehttps://github.com/stripe/stripe-mock/archive/refs/tags/v0.201.0.tar.gz
Last updated2026-05-28T22:23:11Z
Pulseupdated
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicedeclared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namestripe-mock
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

zypper95%

stripe-mock 0.186.0-1.6

Mock HTTP server based on the real Stripe API

https://github.com/stripe/stripe-mock

sudo zypper install stripe-mock
  • License: MIT
  • Category: Unspecified
  • Architecture: x86_64
  • Source Package: stripe-mock
  • 1 dependencies
  • 1 provides
  • normalized package name match
  • Matched by: Stripe Mock
openSUSE Tumbleweed package metadata · download.opensuse.org · openSUSE Tumbleweed package metadata: stripe-mock from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment