Add secure-ws library by sudo-rgorai · Pull Request #22 · fundwave/network-utils

sudo-rgorai · 2025-09-12T09:31:44Z

Add new secure-ws library

Overview

Add secure-ws library to manage websocket connections for Node.js and TypeScript projects.

Motivation

To provide a reusable WebSocket provider for projects requiring real-time communication.
To enable easy integration with existing Express middleware and TypeScript-based codebases.

Resolution

Linked to getfundwave/discussions/issues/445
Closes getfundwave/discussions/issues/477

Features

Core WebSocket Provider:
Implements a modular WebSocket provider in core/web-socket-provider.ts with support for custom protocols and extensibility.
Protocol Codec:
Encapsulates WebSocket protocol encoding/decoding logic in core/ws-protocol-codec.ts to send headers and body in the websocket upgrade handshake
Middleware Support:
Includes utilities for adapting Express-style middleware to WebSocket handlers in utils/middleware-adapter.ts and utils/inject-http-request.ts.

…ol codec

…ad of JWKS-slim

…er instead of JWKS-slim" This reverts commit fe359a5.

…ket-provider

…rkflow

[skip ci]

…orkflow

[skip ci]

This reverts commit f30b8c3.

…sh workflow

Copilot

Pull request overview

Copilot reviewed 17 out of 19 changed files in this pull request and generated 6 comments.

Files not reviewed (1)

secure-ws/package-lock.json: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-09T13:19:16Z

+import { WebSocket } from 'ws';
+import { MockResponse } from '../mocks/express-response';
+import { MockResponse as MockResponseType } from '../types/mock-response';
+import { NextFunction, Request, Response } from 'express';


Response is imported from express but never used in this module. Removing unused imports avoids lint/build failures in projects that enforce noUnusedLocals/noUnusedParameters.

Suggested change

import { NextFunction, Request, Response } from 'express';

import { NextFunction, Request } from 'express';

Copilot · 2026-04-09T13:19:17Z

+  // Merge headers
+  if (httpRequest.headers) {
+    for (const [key, value] of Object.entries(httpRequest.headers)) {
+      request.headers[key.toLowerCase()] = value;


injectHttpRequest unconditionally overwrites existing request headers with values provided via ws.protocol. This lets a client spoof/override headers that may already be set by upstream infrastructure (e.g. x-forwarded-for, cookie, etc.). Consider whitelisting which headers can be injected, namespacing them, or only setting a header if it is not already present.

Suggested change

// Merge headers

if (httpRequest.headers) {

for (const [key, value] of Object.entries(httpRequest.headers)) {

request.headers[key.toLowerCase()] = value;

// Merge headers without overwriting headers already present on the request

if (httpRequest.headers) {

for (const [key, value] of Object.entries(httpRequest.headers)) {

const normalizedKey = key.toLowerCase();

if (request.headers[normalizedKey] === undefined) {

request.headers[normalizedKey] = value;

}

Copilot · 2026-04-09T13:19:17Z

+  public handleUpgrade = (request: IncomingMessage, socket: Duplex, head: Buffer) => {
+    const { pathname } = new URL(request.url!, 'wss://base.url');
+
+    if (this.routes[pathname]) {
+      this.server.handleUpgrade(request, socket, head, (ws: ClientSocket) => {
+
+        ws.id = `${Date.now()}-${randomUUID()}`;
+        this.clientSockets.set(ws.id, ws);
+        ws.on('close', () => {
+          this.clientSockets.delete(ws.id);
+        });
+
+        this.server.emit('connection', ws, request);
+      });


The README/PR description claims middleware runs "during the upgrade handshake", but the current flow upgrades the connection in handleUpgrade() and only runs onConnect middleware later in the 'connection' handler. If the intent is to reject unauthenticated clients before the WebSocket is established, the middleware (or an equivalent auth step) needs to run before calling server.handleUpgrade() (or use verifyClient/custom handleUpgrade gating) and respond with an HTTP error instead of upgrading first.

Copilot · 2026-04-09T13:19:17Z

+        ws.send(JSON.stringify({ error: res.error }));
+        ws.close(1000, res.error);


On middleware rejection, the code calls ws.send(...) and immediately ws.close(...). In ws, closing right after sending can result in the message being dropped if it hasn't been flushed yet. Consider closing in the send callback (or waiting for the socket to drain) to ensure the client reliably receives the error payload.

Suggested change

ws.send(JSON.stringify({ error: res.error }));

ws.close(1000, res.error);

ws.send(JSON.stringify({ error: res.error }), () => {

ws.close(1000, res.error);

});

Copilot · 2026-04-09T13:19:18Z

+          git commit -a -m "CI: bumps secure-ws to $VERSION" -m "[skip ci]"
+
+      - name: Publish package to npm
+        run: |
+          npm publish --tag $BRANCH_TAG --access public
+


The npm publish step writes only registry=... to ~/.npmrc but does not configure the auth token line (//registry.npmjs.org/:_authToken=...). Unlike the other publish workflows in this repo, this is likely to cause npm publish to fail with an auth error. Consider matching the pattern used in .github/workflows/npm-publish.yml / npm-publish-ssm-env-util.yml by writing the _authToken entry (or using actions/setup-node with registry-url so NODE_AUTH_TOKEN is picked up).

[skip ci]

Copilot

Pull request overview

Copilot reviewed 17 out of 19 changed files in this pull request and generated 6 comments.

Files not reviewed (1)

secure-ws/package-lock.json: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-09T13:37:52Z

+export function runExpressMiddleware(
+  middleware: (req: Request, res: MockResponseType, next: NextFunction) => void,
+  request: IncomingMessage,
+  socket: WebSocket


runExpressMiddleware accepts middleware as (req: Request, res: MockResponseType, next) => void, but routes are typed to accept ExpressMiddleware (req, res: Response, next) => any (see secure-ws/types/express-middleware.ts). This makes the public API type-inconsistent for consumers using strict type-checking. Prefer typing the adapter to accept ExpressMiddleware and cast/wrap the mock response internally to satisfy Response (or extend the mock to implement the needed subset).

Copilot · 2026-04-09T13:37:52Z

+- filename: websocket-provider/package-lock.json
+  checksum: 605a2d92b91f08ee577d3b1e7ed38d27eef43573a044608c22466f05ab6eaff7


This file is newly added, but it is already being ignored by Talisman (fileignoreconfig). Adding ignores reduces secret-detection coverage going forward; it’s safer to remove this ignore entry and fix the underlying finding (or add a narrower ignore with justification) so new changes to this file continue to be scanned.

Suggested change

- filename: websocket-provider/package-lock.json

checksum: 605a2d92b91f08ee577d3b1e7ed38d27eef43573a044608c22466f05ab6eaff7

Copilot · 2026-04-09T13:37:53Z

+          git config user.name "fundabot"
+          git commit -a -m "CI: bumps secure-ws to $VERSION" -m "[skip ci]"
+
+      - name: Publish package to npm


This workflow publishes on every push to any branch (no if: github.ref_name == 'main' guard on the publish step), and it does not set NODE_AUTH_TOKEN (unlike existing npm publish workflows in this repo). This is likely to either fail publishes due to missing auth or unintentionally publish prerelease builds from feature branches. Align with .github/workflows/npm-publish.yml by restricting publish to main (or explicitly documenting/restricting which branches are allowed) and configuring npm auth via NODE_AUTH_TOKEN/secrets.

Suggested change

- name: Publish package to npm

- name: Publish package to npm

if: ${{ github.ref_name == 'main'}}

env:

NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

Copilot · 2026-04-09T13:37:53Z

+    "build": "tsc"
+  },
+  "author": "The Fundwave Authors",
+  "license": "ISC",


The declared package license (ISC) doesn’t match the README’s stated license (MIT). This should be consistent to avoid legal/packaging confusion; update either package.json or README.md so they agree.

Suggested change

"license": "ISC",

"license": "MIT",

Copilot · 2026-04-09T13:37:53Z

+# secure-ws
+
+secure-ws is a TypeScript library for secure WebSocket servers that lets you run Express-style middleware during the upgrade handshake, ensuring unauthenticated connections are never left open.


This repository doesn’t appear to have a .github/instructions/ directory with Copilot instructions for TypeScript/Node files (only custom-instructions/ exists). If this repo relies on GitHub Copilot instruction files, add the appropriate instruction files under .github/instructions for this new package to match the expected project layout.

Copilot · 2026-04-09T13:37:53Z

+export class WebSocketProvider {
+  public server: WebSocketServer;
+  public clientSockets: Map<string, ClientSocket>;
+  private routes: Record<string, AddRouteParams>;
+
+  constructor() {
+    this.server = new WebSocketServer({ noServer: true });
+    this.server.on('connection', this.handleConnection);
+    this.routes = {};
+    this.clientSockets = new Map();
+  }


This new WebSocket provider introduces several non-trivial behaviors (upgrade routing, protocol decoding, middleware execution, message decoding) but there are no automated tests added for them. Since the repo already has test coverage for other published packages (e.g., jwks-slim/tests/*), consider adding tests for at least: middleware rejection/acceptance paths, protocol injection, and message decode error handling.

[skip ci]

…Provider

[skip ci]

Copilot

Pull request overview

Copilot reviewed 17 out of 19 changed files in this pull request and generated 11 comments.

Files not reviewed (1)

secure-ws/package-lock.json: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-16T13:05:47Z

+        if (allowedOrigin === '*') return true;
+        if (allowedOrigin instanceof RegExp) {
+          return allowedOrigin.test(origin || '');
+        }
+        const regex = new RegExp(`^${allowedOrigin.replace(/\*/g, '.*')}$`);
+        return regex.test(origin || '');


Origin allowlist matching builds a RegExp directly from allowedOrigin without escaping regex metacharacters (e.g., .), so values like https://example.com will match unintended origins. Escape the string before replacing *, or avoid regex and use exact string comparison when no wildcard is present.

Suggested change

if (allowedOrigin === '*') return true;

if (allowedOrigin instanceof RegExp) {

return allowedOrigin.test(origin || '');

}

const regex = new RegExp(`^${allowedOrigin.replace(/\*/g, '.*')}$`);

return regex.test(origin || '');

const requestOrigin = origin || '';

if (allowedOrigin === '*') return true;

if (allowedOrigin instanceof RegExp) {

return allowedOrigin.test(requestOrigin);

}

if (!allowedOrigin.includes('*')) {

return allowedOrigin === requestOrigin;

}

const escapedAllowedOrigin = allowedOrigin

.replace(/[|\\{}()[\]^$+?.]/g, '\\$&')

.replace(/\*/g, '.*');

const regex = new RegExp(`^${escapedAllowedOrigin}$`);

return regex.test(requestOrigin);

Copilot · 2026-04-16T13:05:47Z

+
+      origins.push(...FUNDWAVE_DOMAIN_PATTERNS);
+


FUNDWAVE_DOMAIN_PATTERNS are always appended to the allowlist, so a consumer cannot configure origins to only their own domains. Consider making these patterns opt-in (config flag) or removing them from the generic library to avoid unintentionally broad origin access.

Copilot · 2026-04-16T13:05:48Z

+    try {
+      middleware(request as Request, mockRes as MockResponseType, next);
+    } catch (error) {
+      console.error("Middleware exception:", error);
+      if (!nextCalled) {
+        nextCalled = true;
+        resolve({ success: false, error: error.message || 'Middleware exception' });
+      }
+    }


Async Express middleware (declared async / returning a Promise) isn't handled: any rejection after an await won't be caught by the surrounding try/catch, and the returned Promise is ignored. Capture the return value from middleware(...) and, if it's a Promise, attach .catch(next) (and/or await it) so failures reliably reject the connection.

Copilot · 2026-04-16T13:05:48Z

+import express from "express";
+import { WebSocketProvider } from 'secure-ws';
+
+const wsApp = new WebSocketProvider();


README usage constructs new WebSocketProvider() without arguments, but the constructor currently requires { allowedOrigins: string }. Either update the README example to pass allowedOrigins, or make the constructor parameter optional with a secure default (ideally explicit allowlist required).

Suggested change

const wsApp = new WebSocketProvider();

const wsApp = new WebSocketProvider({

allowedOrigins: "https://your-app.example.com"

});

Copilot · 2026-04-16T13:05:48Z

+          default: "${{ env.BRANCH == 'main' && 'patch' || 'prerelease' }}"
+          PACKAGEJSON_DIR: "secure-ws"
+          preid: "${{ env.BRANCH }}"
+          skip-tag: "true"


Non-main branch names often contain / (e.g., feature/foo), but preid: "${{ env.BRANCH }}" and npm publish --tag $BRANCH_TAG will then use an invalid semver prerelease identifier / npm dist-tag. Sanitize github.ref_name for semver/tag safety (e.g., replace / with -).

Copilot · 2026-04-16T13:05:48Z

+secure-ws is a TypeScript library for secure WebSocket servers that lets you run Express-style middleware during the upgrade handshake, ensuring unauthenticated connections are never left open.
+


The README/PR description says middleware runs "during the WebSocket upgrade handshake", but the current implementation runs middleware in the connection handler (after handleUpgrade completes). If handshake-time rejection is required, consider moving auth/validation to handleUpgrade (e.g., via verifyClient / manual HTTP response) or update the docs to reflect the actual behavior (connection is briefly established then closed).

Copilot · 2026-04-16T13:05:49Z

+  "scripts": {
+    "test": "echo \"Error: no test specified\" && exit 1",
+    "build": "tsc"
+  },


This new library introduces significant behavior (origin validation, protocol decoding, middleware adaptation) but the package has no real test runner (npm test always exits 1) and there are no automated tests. Add unit/integration tests (similar to jwks-slim's Jest setup) to cover origin allowlisting, middleware success/failure, and protocol encode/decode roundtrips.

Copilot · 2026-04-16T13:05:49Z

+      if (!res.success) {
+        console.error("Middleware rejected connection:", res.error);
+        ws.send(JSON.stringify({ error: res.error }));
+        ws.close(1000, res.error);


When middleware rejects a connection, the socket is closed with code 1000 (normal closure). Use a more appropriate close code like 1008 (policy violation) so clients can reliably distinguish authentication/authorization failures from normal disconnects.

Suggested change

ws.close(1000, res.error);

ws.close(1008, res.error);

Copilot · 2026-04-16T13:05:49Z

+      - name: Push changes
+        uses: ad-m/github-push-action@master
+        with:
+          github_token: ${{ env.GITHUB_TOKEN }}


On main you generate a GitHub App token for checkout, but the push step always uses ${{ env.GITHUB_TOKEN }} (set to secrets.GITHUB_TOKEN). If main is protected, this can prevent pushing the version-bump commit. Use steps.generate_token.outputs.token for the push step on main (or set env.GITHUB_TOKEN conditionally).

Suggested change

github_token: ${{ env.GITHUB_TOKEN }}

github_token: ${{ github.ref_name == 'main' && steps.generate_token.outputs.token || secrets.GITHUB_TOKEN }}

Copilot · 2026-04-16T13:05:49Z

+          git config user.name "fundabot"
+          git commit -a -m "CI: bumps secure-ws to $VERSION" -m "[skip ci]"
+
+      - name: Publish package to npm


npm publish requires npm authentication, but this workflow doesn't set NODE_AUTH_TOKEN / .npmrc (unlike the existing npm-publish.yml workflow). Add the npm token setup (or OIDC-based auth if that’s what you intend) so publishing doesn’t fail at runtime.

Suggested change

- name: Publish package to npm

- name: Publish package to npm

env:

NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

[skip ci]

Rahul Gorai added 6 commits September 12, 2025 14:48

feat: Implement WebSocket provider with middleware support and protoc…

7213cd9

…ol codec

temp: update workflow to release and publish websocket-provider inste…

fe359a5

…ad of JWKS-slim

Revert "temp: update workflow to release and publish websocket-provid…

3d31022

…er instead of JWKS-slim" This reverts commit fe359a5.

feat: Add GitHub Actions workflow for releasing and publishing websoc…

64a4671

…ket-provider

fix: Update workflow trigger to push on websocket-provider branch

62657b4

fix: Rename job from 'test' to 'setup' and update dependencies for wo…

6603205

…rkflow

sudo-rgorai temporarily deployed to Dev September 15, 2025 10:58 — with GitHub Actions Inactive

fundabot and others added 2 commits September 15, 2025 10:58

CI: bumps websocket-provider to 1.0.1-websocket-provider.0

42c7e43

[skip ci]

fix: Publish websocket-provider package from feature branches

1493375

sudo-rgorai had a problem deploying to Dev September 15, 2025 11:11 — with GitHub Actions Failure

fix: Correct npm command in publish step of workflow

1c36935

sudo-rgorai had a problem deploying to Dev September 15, 2025 11:12 — with GitHub Actions Failure

fix: pass correct flags to npm publish command in publish-websocket w…

95ea7e8

…orkflow

sudo-rgorai had a problem deploying to Dev September 15, 2025 11:23 — with GitHub Actions Failure

Mohit Garg and others added 3 commits September 16, 2025 15:59

rename to secure-ws

36477e8

refactor: remove duplicate websocket-provider and related files

6ff441e

refactor: websocket-provider -> secure-ws in GitHub Actions workflow

421f059

sudo-rgorai temporarily deployed to Dev September 16, 2025 10:39 — with GitHub Actions Inactive

fundabot and others added 2 commits September 16, 2025 10:39

CI: bumps secure-ws to 0.0.2-websocket-provider.0

0958ebb

[skip ci]

fix: add build step before publishing secure-ws package

4a5939f

sudo-rgorai temporarily deployed to Dev September 16, 2025 10:51 — with GitHub Actions Inactive

fundabot and others added 2 commits September 16, 2025 10:51

CI: bumps secure-ws to 0.0.2-websocket-provider.1

024f82a

[skip ci]

fix: add missing files entry in package.json

f0f16c7

sudo-rgorai temporarily deployed to Dev September 16, 2025 11:02 — with GitHub Actions Inactive

fundabot and others added 2 commits September 16, 2025 11:03

CI: bumps secure-ws to 0.0.2-websocket-provider.2

ee8cf47

[skip ci]

Temp: log dir structure after build

f30b8c3

sudo-rgorai had a problem deploying to Dev September 16, 2025 11:21 — with GitHub Actions Failure

Rahul Gorai added 2 commits September 16, 2025 16:52

Revert "Temp: log dir structure after build"

7bf514d

This reverts commit f30b8c3.

fix: remove build job and add it as a step in publish_and_release

c32a879

sudo-rgorai temporarily deployed to Dev September 16, 2025 11:27 — with GitHub Actions Inactive

Copilot started reviewing on behalf of sudo-rgorai April 9, 2026 13:12 View session

fix: include workflow file in push paths for npm publish

daec267

sudo-rgorai had a problem deploying to Dev April 9, 2026 13:13 — with GitHub Actions Failure

fix: update node version to 22 and checkout action to v6 in npm publi…

e1a5169

…sh workflow

sudo-rgorai had a problem deploying to Dev April 9, 2026 13:18 — with GitHub Actions Failure

Copilot AI reviewed Apr 9, 2026

View reviewed changes

fix: update node version to 24 in npm publish workflow

24fb513

sudo-rgorai had a problem deploying to Dev April 9, 2026 13:27 — with GitHub Actions Failure

fix: add repository field to package.json

3460514

Copilot AI review requested due to automatic review settings April 9, 2026 13:31

sudo-rgorai temporarily deployed to Dev April 9, 2026 13:31 — with GitHub Actions Inactive

CI: bumps secure-ws to 0.0.2-websocket-provider.15

f1adbc0

[skip ci]

Copilot started reviewing on behalf of sudo-rgorai April 9, 2026 13:32 View session

Copilot AI reviewed Apr 9, 2026

View reviewed changes

feat: origin validation in WebSocketProvider for cors support

b1b8c8d

sudo-rgorai temporarily deployed to Dev April 16, 2026 12:42 — with GitHub Actions Inactive

CI: bumps secure-ws to 0.0.2-websocket-provider.16

cc88a57

[skip ci]

Copilot AI review requested due to automatic review settings April 16, 2026 12:42

sudo-rgorai review requested due to automatic review settings April 16, 2026 12:42

feat: add FUNDWAVE_DOMAIN_PATTERNS for origin validation in WebSocket…

f0288c7

…Provider

Copilot AI review requested due to automatic review settings April 16, 2026 12:57

sudo-rgorai temporarily deployed to Dev April 16, 2026 12:57 — with GitHub Actions Inactive

CI: bumps secure-ws to 0.0.2-websocket-provider.17

9f75f61

[skip ci]

Copilot started reviewing on behalf of sudo-rgorai April 16, 2026 12:57 View session

Copilot AI reviewed Apr 16, 2026

View reviewed changes

add socket: WebSocket to MockResponse interface.

22da40a

giriparus deployed to Dev May 12, 2026 05:08 — with GitHub Actions Active

CI: bumps secure-ws to 0.0.2-websocket-provider.18

9e7b856

[skip ci]

Copilot AI review requested due to automatic review settings May 12, 2026 05:09

sudo-rgorai review requested due to automatic review settings May 12, 2026 05:09

	import { NextFunction, Request, Response } from 'express';
	import { NextFunction, Request } from 'express';

		ws.send(JSON.stringify({ error: res.error }));
		ws.close(1000, res.error);

		- filename: websocket-provider/package-lock.json
		checksum: 605a2d92b91f08ee577d3b1e7ed38d27eef43573a044608c22466f05ab6eaff7

		# secure-ws

		secure-ws is a TypeScript library for secure WebSocket servers that lets you run Express-style middleware during the upgrade handshake, ensuring unauthenticated connections are never left open.

-        if (allowedOrigin === '*') return true;
-        if (allowedOrigin instanceof RegExp) {
-          return allowedOrigin.test(origin || '');
-        }
-        const regex = new RegExp(`^${allowedOrigin.replace(/\*/g, '.*')}$`);
-        return regex.test(origin || '');
+        const requestOrigin = origin || '';
+        if (allowedOrigin === '*') return true;
+        if (allowedOrigin instanceof RegExp) {
+          return allowedOrigin.test(requestOrigin);
+        }
+        if (!allowedOrigin.includes('*')) {
+          return allowedOrigin === requestOrigin;
+        }
+        const escapedAllowedOrigin = allowedOrigin
+          .replace(/[|\\{}()[\]^$+?.]/g, '\\$&')
+          .replace(/\*/g, '.*');
+        const regex = new RegExp(`^${escapedAllowedOrigin}$`);
+        return regex.test(requestOrigin);

-const wsApp = new WebSocketProvider();
+const wsApp = new WebSocketProvider({
+  allowedOrigins: "https://your-app.example.com"
+});

	github_token: ${{ env.GITHUB_TOKEN }}
	github_token: ${{ github.ref_name == 'main' && steps.generate_token.outputs.token \|\| secrets.GITHUB_TOKEN }}

Conversation

sudo-rgorai commented Sep 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Add new secure-ws library

Overview

Motivation

Resolution

Features

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

sudo-rgorai commented Sep 12, 2025 •

edited

Loading