Skip to content

stripe app#62

Merged
ctate merged 4 commits intomainfrom
ctate/stripe-app
Feb 5, 2026
Merged

stripe app#62
ctate merged 4 commits intomainfrom
ctate/stripe-app

Conversation

@ctate
Copy link
Copy Markdown
Collaborator

@ctate ctate commented Feb 5, 2026

No description provided.

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Feb 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
json-render Ready Ready Preview, Comment Feb 5, 2026 6:54pm

@socket-security
Copy link
Copy Markdown

socket-security bot commented Feb 5, 2026

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​stripe/​ui-extension-tools@​0.0.1761006785100
Added@​json-render/​react@​0.4.0771009991100
Added@​json-render/​core@​0.4.0771009991100
Addedstripe@​13.11.08010010096100
Added@​stripe/​ui-extension-sdk@​9.1.0100100100100100

View full report

@socket-security
Copy link
Copy Markdown

socket-security bot commented Feb 5, 2026

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm safer-buffer is 94.0% likely obfuscated

Confidence: 0.94

Location: Package overview

From: pnpm-lock.yamlnpm/@stripe/ui-extension-tools@0.0.1npm/safer-buffer@2.1.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@ctate ctate merged commit 4ae049f into main Feb 5, 2026
4 of 5 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