Stripeek

v0.1.3 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 11h CLI & Terminal

✓ No known CVEs patched

✓ No known CVEs patched in this version

Topics

devtools stripe stripe-api tui

Summary

AI summary

Adds full webhook support with real‑time TUI display and grouping.

Type	Severity	Summary	CVE
Feature
Feature	Medium	Adds full webhook support to stripeek. Adds full webhook support to stripeek. Source: llm_adapter@2026-06-13 Confidence: high	—
Feature	Low	Allows configuring webhook target via `STRIPEEK_WEBHOOK_TARGET` environment variable. Allows configuring webhook target via `STRIPEEK_WEBHOOK_TARGET` environment variable. Source: granite4.1:30b@2026-06-13-audit Confidence: low	—
Feature	Low	Enables forwarding Stripe webhooks to a local server using `stripe listen --forward-to localhost:4243/webhooks`. Enables forwarding Stripe webhooks to a local server using `stripe listen --forward-to localhost:4243/webhooks`. Source: granite4.1:30b@2026-06-13-audit Confidence: low	—
Feature	Low	Displays incoming webhooks in stripeek's TUI in real time. Displays incoming webhooks in stripeek's TUI in real time. Source: granite4.1:30b@2026-06-13-audit Confidence: low	—
Feature	Low	Provides `r` key to group related requests and webhooks based on `request_id` and object IDs. Provides `r` key to group related requests and webhooks based on `request_id` and object IDs. Source: granite4.1:30b@2026-06-13-audit Confidence: low	—

Full changelog

This release introduces full webhook support:

run with STRIPEEK_WEBHOOK_TARGET=http://localhost:4567 stripeek to point stripeek to your local server that processes Stripe webhooks. there's no need to provide the exact webhook endpoint.
point your stripe listen to stripeek's listening port stripe listen --forward-to localhost:4243/webhooks. The path you set will be the path stripeek forwards the webhooks to, so your local server will receive them at http://localhost:4567/webhooks.
now all the incoming webhooks will be displayed in stripeek's TUI in real time, you can press r to group related requests and webhooks together: the relation is inferred from a combination of request_id and object IDs (subscription, customer, invoice etc.) so even the webhooks tha don't follow the request directly (e.g., from subscription change due to test clock advancing) will be correctly attributed

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Stripeek

Get notified when new releases ship.

About Stripeek