DO NOT MERGE - KEEP FOR CI TESTS Refractor frontend branch from @mohibr by prozacchiwawa · Pull Request #230 · Chia-Network/chia-gaming

prozacchiwawa · 2025-11-20T22:30:57Z

No description provided.

…(experimental)

…ure-based structure - Renamed BramVibe1 feature to CaliforniaPoker - Moved feature into src/features/californiaPoker/ - Separated UI components into components/ directory - Added utils/ folder for logic helpers (deck creation, hand evaluation, etc.) - Moved constants into constants/ folder - Extracted shared interfaces and types to src/types/ - Organized CalPoker feature similarly with its own components/ folder - Improved file naming consistency and imports for maintainability

…to RefractorFrontend

…m URL copy dialog

…to RefractorFrontend

…etwork/chia-gaming into RefractorFrontend

- Updated main game UI layout and visuals - Refined game logs UI for better readability - Added toast notifications for game updates - Improved lobby UI structure and styling - Implemented expandable sections for chat and connected players (mutually exclusive expand/shrink) - Fixed header responsiveness across breakpoints

Convert UI components from MUI/Sx to Tailwind utility classes (e.g. WalletConnect.tsx, WalletConnectHeading.tsx) Add designrift CSS variables and aliases for light/dark theming in index.css Configure Tailwind v4 (tailwind.config.ts): map CSS vars to tokens, enable darkMode: "class", and update content paths Fix responsive breakpoint ordering and remove duplicate fallback rules that overrode media queries Ensure Tailwind-generated utilities are used (removed hardcoded fallbacks added during debugging) Add dark/light toggle with localStorage persistence and small UX tweaks in App.tsx Rebuild and verify index.css; confirm Docker mounts for resources/gaming-fe/dist/* do not conflict with the build output Notes: Run cd resources/gaming-fe && yarn build and verify UI in browser/Docker. If utilities are missing, ensure tailwind.config.ts scans files containing class strings (avoid runtime-generated classnames).

…Network/chia-gaming into RefractorFrontend

…-Network/chia-gaming into RefractorFrontend

…nt so every button is using the same properties

…t into separate components

This reverts commit f9fcaf9, reversing changes made to f059293.

…alisp" This reverts commit f059293, reversing changes made to 553513c.

socket-security · 2025-11-26T13:03:59Z

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		License policy violation: npm `caniuse-lite` under CC-BY-4.0 License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (npm metadata) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/LICENSE) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/package.json) From: `?` → `npm/css-minimizer-webpack-plugin@7.0.2` → `npm/webpack@5.102.1` → `npm/@babel/preset-env@7.28.5` → `npm/@babel/core@7.28.5` → `npm/caniuse-lite@1.0.30001749` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/caniuse-lite@1.0.30001749`. 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.
Warn		License policy violation: npm `caniuse-lite` under CC-BY-4.0 License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (npm metadata) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/LICENSE) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/package.json) From: `?` → `npm/css-minimizer-webpack-plugin@7.0.2` → `npm/@babel/preset-env@7.28.5` → `npm/@babel/core@7.28.5` → `npm/webpack@5.103.0` → `npm/caniuse-lite@1.0.30001759` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/caniuse-lite@1.0.30001759`. 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.
Warn		License policy violation: npm `node-forge` under GPL-2.0 License: GPL-2.0 - the applicable license policy does not allow this license (4) (package/LICENSE) From: `?` → `npm/webpack-dev-server@5.2.2` → `npm/node-forge@1.3.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/node-forge@1.3.3`. 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.
Warn		Potential code anomaly (AI signal): npm `@tailwindcss/oxide-wasm32-wasi` is 100.0% likely to have a medium risk anomaly Notes: Overall, this code fragment is a standard and legitimate binding/runtime infrastructure for Node.js native addon interoperability (EMNAPI). There is no evidence of data exfiltration, remote control, backdoors, or malware behavior within this snippet. The primary security considerations relate to the complexity and correct handling of finalizers, weak references, and policy-driven warning paths; misconfiguration or misuse by host applications could introduce risk, but the code itself does not demonstrate malicious activity. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/@tailwindcss/cli@4.1.15` → `npm/@tailwindcss/oxide-wasm32-wasi@4.1.15` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@tailwindcss/oxide-wasm32-wasi@4.1.15`. 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.
Warn		Potential code anomaly (AI signal): npm `cacache` is 100.0% likely to have a medium risk anomaly Notes: The analyzed code is a straightforward content-cache retrieval and streaming utility. It reads from a cache using an index, supports digest-based access, and optionally memoizes results. There is no evidence of malicious behavior, data exfiltration, backdoors, or external network activity within this module. The security risk appears low, assuming the surrounding system properly manages cache integrity and does not expose untrusted cache contents without validation. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/ts-node-dev@2.0.0` → `npm/sqlite3@5.1.7` → `npm/webpack-dev-server@5.2.2` → `npm/@babel/cli@7.28.3` → `npm/jest@30.2.0` → `npm/@tailwindcss/cli@4.1.15` → `npm/cacache@20.0.3` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/cacache@20.0.3`. 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.
Warn		Potential code anomaly (AI signal): npm `engine.io-client` is 100.0% likely to have a medium risk anomaly Notes: The analyzed code fragment aligns with a legitimate, minified transport library (Engine.IO-like) implementing multiple transports, handshake flows, and binary data handling. There is no concrete evidence of malware, backdoors, or data exfiltration in this fragment. The minified form is typical for public libraries. Recommend validating exact package version against authoritative sources and performing a full dependency-SCA for the entire package to rule out supply-chain concerns. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/socket.io-client@4.8.1` → `npm/engine.io-client@6.6.2` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/engine.io-client@6.6.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.
Warn		Potential code anomaly (AI signal): npm `fs-extra` is 100.0% likely to have a medium risk anomaly Notes: The analyzed code is a standard, legitimate implementation of a recursive copy utility (copySync) from the fs-extra library. It includes typical safeguards (type checks, destination directory creation, overwrite logic, symlink handling, and optional timestamp preservation) and does not exhibit any malicious behavior such as data exfiltration, remote communication, backdoors, or code injection. The warning about preserveTimestamps on ia32 is a benign, user-facing message. Overall security risk is low, with normal filesystem side effects expected. If any concern exists, it would be about untrusted path manipulation via the src/dest, but this is inherent to any filesystem copy utility and mitigated by the provided option hooks (filter, dereference, etc.). Confidence: 1.00 Severity: 0.60 From: `?` → `npm/@shadcn/ui@0.0.4` → `npm/fs-extra@11.3.2` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/fs-extra@11.3.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.
Warn		Potential code anomaly (AI signal): npm `minipass-fetch` is 100.0% likely to have a medium risk anomaly Notes: No evidence of malicious behavior or supply-chain sabotage within this code fragment. The code adheres to standard fetch-like behavior with conventional TLS/config handling. Potential security considerations include the ability to disable TLS verification via an environment variable (a known risk if misused) but this is typical for Node.js TLS configurations and not a deliberate backdoor. Overall risk is moderate due to TLS verification control but not due to malicious intent in this module. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/ts-node-dev@2.0.0` → `npm/sqlite3@5.1.7` → `npm/webpack-dev-server@5.2.2` → `npm/@babel/cli@7.28.3` → `npm/jest@30.2.0` → `npm/@tailwindcss/cli@4.1.15` → `npm/minipass-fetch@5.0.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/minipass-fetch@5.0.0`. 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.
Warn		Potential code anomaly (AI signal): npm `node-gyp` is 100.0% likely to have a medium risk anomaly Notes: The code is a legitimate Windows registry query and filesystem readability utility, with no inherent malware or backdoors. Primary security concerns are data exposure through verbose logging and the potential misuse of reg.exe with untrusted inputs. Mitigations include restricting input sources, redacting sensitive outputs in logs, and ensuring callers handle registry data securely. Overall security risk is moderate due to sensitive operations and logging exposure, but no active malicious behavior detected. Confidence: 1.00 Severity: 0.60 From: `?` → `npm/ts-node-dev@2.0.0` → `npm/sqlite3@5.1.7` → `npm/webpack-dev-server@5.2.2` → `npm/@babel/cli@7.28.3` → `npm/jest@30.2.0` → `npm/@tailwindcss/cli@4.1.15` → `npm/node-gyp@12.1.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/node-gyp@12.1.0`. 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

…, and improve UI components - Modified `build-and-run.sh` to include building the `lobby-view` frontend and added necessary volume mounts for Docker. - Updated `package.json` to include new dependencies: `@radix-ui/react-scroll-area`, `@radix-ui/react-separator`, `clsx`, `tailwind-merge`, and `tw-animate-css`. - Adjusted `tsconfig.json` to set base URL and paths for module resolution. - Enhanced UI components in `App.tsx`, `GameRedirectPopup.tsx`, and `Calpoker` to improve styling and layout. - Refactored `HandDisplay` component for better responsiveness and layout consistency. - Removed unused `custom.d.ts` file.

socket-security · 2025-11-27T12:51:58Z

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

Package	Supply Chain Security	Quality	Maintenance
npm/@radix-ui/react-separator@1.1.8
npm/@shadcn/ui@0.0.4
npm/@types/express@4.17.21
npm/@radix-ui/react-dialog@1.1.15
npm/@radix-ui/react-tooltip@1.2.8
npm/@radix-ui/react-scroll-area@1.2.10
npm/typescript-eslint@8.47.0 ⏵ 8.46.0			^-1
npm/typescript-eslint@8.47.0 ⏵ 8.48.1
npm/@types/qrcode@1.5.6 ⏵ 1.5.5
npm/@tailwindcss/cli@4.1.15
npm/@types/node@20.19.24 ⏵ 20.17.43
npm/@types/cors@2.8.17
npm/@emotion/styled@11.14.0
npm/tailwindcss@4.1.15
npm/autoprefixer@10.4.22 ⏵ 10.4.21		⁺³
npm/tailwind-merge@3.4.0
npm/@mui/icons-material@7.3.5 ⏵ 7.3.6			⁺²
npm/@mui/icons-material@7.3.5 ⏵ 7.1.0	^-2	⁺¹	⁺²
npm/tw-animate-css@1.4.0
npm/dotenv@16.5.0
npm/ts-jest@29.4.5 ⏵ 29.4.4			^-4
npm/prettier@3.7.4
npm/@mui/material@7.3.5 ⏵ 7.3.6		⁺¹	⁺²
npm/@rollup/plugin-node-resolve@16.0.2
npm/axios@1.13.2 ⏵ 1.12.2	⁺¹
npm/ts-jest@29.4.5 ⏵ 29.4.6		⁺¹
npm/lucide-react@0.552.0 ⏵ 0.555.0	⁺¹	⁺¹
npm/@eslint/js@9.38.0 ⏵ 9.37.0			⁺²
npm/eslint@9.38.0 ⏵ 9.37.0
npm/zod@3.24.4
npm/prettier@3.5.3

View full report

- Enhanced the UI of the California Poker game by adjusting layout and styling in `index.tsx`, `HandDisplay.tsx`, and `GameBottomBar.tsx`. - Added responsive design improvements in CSS for better usability on smaller screens. - Refactored code to remove unused variables and streamline functionality.

- Enhanced the layout and styling of the GameLog, HandDisplay, and GameBottomBar components for better user experience. - Updated CSS for consistent spacing and improved responsiveness. - Refactored card rendering logic in the Card component for cleaner code and better performance.

- Improved layout and styling in the Game component for better user experience, including a new card layout for shutdown state. - Simplified background styling in App component by removing inline styles. - Updated GameBottomBar for better mobile responsiveness and visual clarity. - Removed unused state variables in lobby components to streamline code.

- Updated the components.json schema URL and specified the Tailwind CSS config file. - Refactored utility paths in aliases for better module resolution. - Added new dependencies for Radix UI components and Floating UI for enhanced UI functionality. - Introduced new PNG image support and created type definitions for image imports. - Improved styling and layout in various components, including Game, QRCodeModal, and WaitingScreen, for better user experience. - Streamlined code in WalletBadge and WalletConnect components, enhancing readability and maintainability. - Added new UI components for buttons, dialogs, and tooltips to standardize UI elements across the application.

…ion flag, but does nothing else. Implements data suspension so the ui doesn't change while suspended.

…terval and then resume the ui correctly afterward.

- Improved styling and layout in QRCodeModal for better mobile responsiveness and user experience. - Updated variable names in California Poker to clarify functionality, changing components in CreateRoomDialog for consistency and improved UI.

…pokerOutcome decoding

- Removed unused CssBaseline imports from index files in both gaming and lobby views for cleaner code. - Updated GameLog and QRCodeModal components to enhance layout and responsiveness. - Adjusted styles in WaitingScreen and CreateRoomDialog for better user experience and consistency. - Improved card rendering logic in HandDisplay and Card components for better performance and clarity.

…ork/chia-gaming into RefractorFrontend

- Replaced the Expand icon with ChevronDown in GameLog for better visual consistency. - Changed border color in WaitingScreen to enhance UI clarity. - Adjusted layout in CaliforniaPoker to streamline component structure and improve responsiveness. - Updated CardContent to modify margin for better spacing. - Enhanced HandDisplay to ensure proper z-index for winner/tie indicators. - Introduced SORT_ANIMATION_DURATION constant for animation consistency. - Updated CreateRoomDialog styling for improved user experience.

…onents - Changed Docker image from calpoker:latest to chia-latest:latest for consistency. - Refactored GameLog to reverse log entries for better display order. - Integrated makeDescription utility in CaliforniaPoker for improved hand description handling. - Added state management for player and opponent display texts in CaliforniaPoker. - Enhanced card swapping logic to ensure accurate updates in the UI.

…d functionality - Updated GameLog to display log entries in original order. - Adjusted layout in CaliforniaPoker for better responsiveness and visual hierarchy. - Enhanced card swapping logic to accurately reflect player and opponent hands. - Improved hand description formatting in makeDescription utility for clearer output. - Streamlined HandDisplay component to remove unnecessary title rendering.

prozacchiwawa and others added 30 commits October 9, 2025 17:13

Add the ability to host react+tailwind code like comes out of claude …

d9ac23d

…(experimental)

Merge up

361b5f9

Merge up

9f108c2

Merge branch 'main' of https://github.com/Chia-Network/chia-gaming in…

c3f83bf

…to RefractorFrontend

feat(game-ui): update layout, improve logs, add game selector and roo…

bf39c63

…m URL copy dialog

Merge branch 'main' of https://github.com/Chia-Network/chia-gaming in…

1c1e44f

…to RefractorFrontend

Updated Code with Animation

3fdf113

Merge branch '20251030-add-last-outcome' of https://github.com/Chia-N…

526bc04

…etwork/chia-gaming into RefractorFrontend

Updated Frontend with Bram Vibe and new design

fd12f0f

wip, but tests passing

b55d13d

reverse unintended

1e05857

remove spam

0c9b8f6

set chiavdf version

a1a2e02

Merge branch '20251108-fix-tests-and-log' of https://github.com/Chia-…

7054c03

…Network/chia-gaming into RefractorFrontend

Fix game merge, tests passing again, swap player displays at end

5f5ef9d

Make a bit more room

44fc6b6

More tightening

50847d0

More aggressive

75781d4

try to save some more space

794a1ba

remove more stuff that used to be relevant but isn't anymore

560a91c

feat: Added Theme Colors

5feeb82

Merge branch '20251117-fix-game-log-merge' of https://github.com/Chia…

5060d15

…-Network/chia-gaming into RefractorFrontend

feat: Added theme colors to every page , added the new button compone…

c30231e

…nt so every button is using the same properties

feat: refactor(lobby): extract ActiveRooms, ConnectedPlayers, and Cha…

1fdb15e

…t into separate components

Revert "Merge pull request #226 from Chia-Network/20251114-install-doc"

5dd8cf2

This reverts commit f9fcaf9, reversing changes made to f059293.

Revert "Merge pull request #225 from Chia-Network/20251112-update-chi…

d5fcec0

…alisp" This reverts commit f059293, reversing changes made to 553513c.

Builds, testing

7776378

aqk previously approved these changes Nov 21, 2025

View reviewed changes

aqk changed the title ~~Refractor frontend branch from @mohibr~~ DO NOT MERGE - KEEP FOR CI TESTS Refractor frontend branch from @mohibr Nov 25, 2025

Nob0dy and others added 2 commits November 26, 2025 18:00

feat: added lab-348 : confirmation dialog before the handShake

f677a68

test: signed commit

2ae2f6b

silverthreadlabs-mohib-r dismissed aqk’s stale review via 2ae2f6b November 26, 2025 13:02

silverthreadlabs-mohib-r and others added 21 commits November 28, 2025 18:00

Merge remote-tracking branch 'origin/main' into 20251202-integrate-demo

0627b68

Add clipboard patch

4a6550f

Null animation (sets supsended for animation duration and sets animat…

ebe878e

…ion flag, but does nothing else. Implements data suspension so the ui doesn't change while suspended.

Suspend flag is plumbed in. We remember the cards over the suspend in…

37d10d9

…terval and then resume the ui correctly afterward.

State machine carved out

212fb88

Fix subsequent turn?

5e8bb37

restore 'click to continue' after game

fa6dea9

start removing fluff

a7fa0be

revert

5906578

Make alice and bob-ness match in game ui and log. fix more of the Cal…

fb9eb01

…pokerOutcome decoding

remove extra gunk

78617f4

Merge branch '20251203-fix-animation' of https://github.com/Chia-Netw…

7580849

…ork/chia-gaming into RefractorFrontend

bramcohen closed this Apr 7, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

DO NOT MERGE - KEEP FOR CI TESTS Refractor frontend branch from @mohibr#230

DO NOT MERGE - KEEP FOR CI TESTS Refractor frontend branch from @mohibr#230
prozacchiwawa wants to merge 59 commits intomainfrom
RefractorFrontend

prozacchiwawa commented Nov 20, 2025

Uh oh!

socket-security Bot commented Nov 26, 2025 •

edited

Loading

Uh oh!

socket-security Bot commented Nov 27, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

prozacchiwawa commented Nov 20, 2025

Uh oh!

socket-security Bot commented Nov 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented Nov 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

socket-security Bot commented Nov 26, 2025 •

edited

Loading

socket-security Bot commented Nov 27, 2025 •

edited

Loading