Skip to content

chore(deps): @profullstack/x402-gateway ^0.15.1, never charge sign-in or app paths - #16

Merged
ralyodio merged 1 commit into
mainfrom
chore/x402-gateway-0.15.1
Oct 28, 2026
Merged

ralyodio merged 1 commit into
mainfrom
chore/x402-gateway-0.15.1

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

Since x402-gateway 0.8, a stale (Chrome two years behind) or headless browser string has been answered 402 on every path, including /login, /signup, OAuth callbacks, /api/auth/*, /dashboard and checkout. Reproduced fleet-wide 2026-10-28 with a Chrome/120 UA. An agent whose CoinPay OAuth token lapsed could not sign back in.

0.15 (profullstack/x402-gateway#24, #25) exports APP_PATHS: sign-in, oauth, account, dashboard, checkout, pay, webhook and health paths, plus any /api/ route with an auth/oauth/callback/webhook/health segment. Those are never charged, and content pages still are. This is a lockfile-only bump with no config change.

🤖 Generated with Claude Code

… or app paths

Since gateway 0.8 a stale or headless Chrome string was answered 402 on
/login, /signup, OAuth callbacks and /api/auth; 0.15 never charges those.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​profullstack/​x402-gateway@​0.13.1 ⏵ 0.15.184 -4100100 +197 +1100

View full report

@ralyodio
ralyodio merged commit 80211a0 into main Oct 28, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant