pkg.soopen package index

brew / Rang 7731

stripe-mock mit Homebrew, zypper installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für stripe-mock in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install stripe-mock

local Homebrew formula metadata

Linux

openSUSE zypperverifiziert · 92%
sudo zypper install stripe-mock

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

Überblick

Paketzusammenfassung

Mock HTTP server that responds like the real Stripe API

Befehle und Aliase

  • stripe-mock

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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.

Sicherheitslage

Risikostufe: orange

formula declares a Homebrew service.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • formula declares a Homebrew service

Signale

  • metadata:service

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Formelmetadaten deklarieren einen Service- oder Daemon-Block.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
stripe-mockcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-08-04
Manager-Version0.202.0
Manager aktualisiert2026-07-26
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.202.0

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

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:stripe-mock
Version0.202.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/stripe-mock
Homepagehttps://github.com/stripe/stripe-mock
Repositoryhttps://github.com/stripe/stripe-mock
LizenzMIT
Quellarchivhttps://github.com/stripe/stripe-mock/archive/refs/tags/v0.202.0.tar.gz
Zuletzt aktualisiert2026-07-26T04:03:47+02:00
Pulseupdated
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstdeclared

Registry-Fakten

Details aus der Quelldatenbank

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-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

zypper95%

stripe-mock 0.201.0-1.3

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 Abhängigkeiten
  • 1 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Stripe Mock
openSUSE Tumbleweed package metadata · download.opensuse.org · openSUSE Tumbleweed package metadata: stripe-mock from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

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