test: add Vitest alongside Jest by cryptodev-2s · Pull Request #10546 · MetaMask/core

cryptodev-2s · 2026-09-28T20:17:56Z

Explanation

Adds Vitest alongside Jest so packages can migrate one at a time.

References

Checklist

I've updated the test suite for new or updated code as appropriate
I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
I've communicated my changes to consumers by updating changelogs for packages I've changed
- Not applicable, test only change. Carries the no-changelog label.
I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them
- None.

Note

Medium Risk
Changes monorepo-wide test execution, lint targeting, and Yarn constraints; dual-runner drift is possible until all packages leave the Jest allowlist.

Overview
Adds Vitest as a second unit-test runner so workspaces can migrate off Jest incrementally. A new test-runner-package-map.cjs allowlists existing packages on Jest; everything else is treated as Vitest (new packages are expected to use Vitest only).

Tooling: Root adds vitest, vite, and Istanbul coverage deps, shared vitest.config.packages.mjs, and tests/vitest/* setup (custom matchers, nock, node-fetch for interceptable HTTP). oxlint now loads Jest vs Vitest rule sets from workspace-aware globs. yarn constraints assert the correct test / test:watch / test:unit scripts per runner. Root test:packages runs each workspace’s test via yarn workspaces foreach instead of a single Jest invocation.

Jest path: Shared Jest helpers gain explicit @jest/globals imports; oxlint suppressions for those files are dropped. Packages with type tests (messenger, utils) run test:types before test:unit.

^{Reviewed by Cursor Bugbot for commit 3a2a6d2. Bugbot is set up for automated code reviews on this repo. Configure here.}

socket-security · 2026-09-28T20:18:44Z

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@metamask/oxlint-config-vitest@0.1.1
	@vitest/coverage-istanbul@5.0.3
	vitest@5.0.3
	vite@8.3.4

View full report

socket-security · 2026-09-28T20:18:46Z

Warning

MetaMask internal reviewing guidelines:

Do not ignore-all
Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
@SocketSecurity ignore npm/PACKAGE@VERSION

Priority	Alert (click "▶" to expand/collapse)	Action
	Potential code anomaly (AI signal): npm `es-module-lexer` is 74.0% likely to have a medium risk anomaly Notes: A WebAssembly-backed parser wrapper (package/dist/lexer.js) executes substrings extracted from untrusted input using (0, eval) during parsing, enabling arbitrary JavaScript execution if attacker-controlled data reaches the eval path. The threat also includes potential sensitive data leakage through error messages. Disable parse() on untrusted input or sandbox/replace builds to mitigate this risk. Confidence: 0.74 Severity: 0.78 From: package.json → `npm/@docusaurus/core@3.10.2` → `npm/@docusaurus/theme-common@3.10.2` → `npm/@docusaurus/types@3.10.2` → `npm/@docusaurus/plugin-content-docs@3.10.2` → `npm/@docusaurus/preset-classic@3.10.2` → `npm/@easyops-cn/docusaurus-search-local@0.55.3` → `npm/jest@30.5.2` → `npm/vitest@5.0.3` → `npm/raw-loader@4.0.2` → `npm/es-module-lexer@2.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/es-module-lexer@2.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 `es-module-lexer` is 70.0% likely to have a medium risk anomaly Notes: A WASM-backed parser wrapper copies caller input into WASM memory and conditionally executes eval() on substrings that resemble quoted literals, creating a potential code-execution risk in the calling process. Error messages may include slices of input, increasing the chance of sensitive data exposure; the embedded WASM payload is opaque and could contain additional, unseen behaviors. Confidence: 0.70 Severity: 0.70 From: package.json → `npm/@docusaurus/core@3.10.2` → `npm/@docusaurus/theme-common@3.10.2` → `npm/@docusaurus/types@3.10.2` → `npm/@docusaurus/plugin-content-docs@3.10.2` → `npm/@docusaurus/preset-classic@3.10.2` → `npm/@easyops-cn/docusaurus-search-local@0.55.3` → `npm/jest@30.5.2` → `npm/vitest@5.0.3` → `npm/raw-loader@4.0.2` → `npm/es-module-lexer@2.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/es-module-lexer@2.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
	Network access: npm `vitest` in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: package.json → `npm/vitest@5.0.3` ℹ Read more on: This package \| This alert \| What is network access? 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/vitest@5.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
	Environment variable access: npm `obug` reads DEBUG Env Vars: DEBUG Location: Package overview From: package.json → `npm/vitest@5.0.3` → `npm/@vitest/coverage-istanbul@5.0.3` → `npm/obug@2.2.1` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/obug@2.2.1`. 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
	Environment variable access: npm `obug` Location: Package overview From: package.json → `npm/vitest@5.0.3` → `npm/@vitest/coverage-istanbul@5.0.3` → `npm/obug@2.2.1` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/obug@2.2.1`. 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
	Environment variable access: npm `rolldown` reads NAPI_RS_NATIVE_LIBRARY_PATH Env Vars: NAPI_RS_NATIVE_LIBRARY_PATH Location: Package overview From: package.json → `npm/vite@8.3.4` → `npm/rolldown@1.2.13` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/rolldown@1.2.13`. 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
	Environment variable access: npm `rolldown` Env Vars: NAPI_RS_ENFORCE_VERSION_CHECK Location: Package overview From: package.json → `npm/vite@8.3.4` → `npm/rolldown@1.2.13` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/rolldown@1.2.13`. 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
	Environment variable access: npm `rolldown` reads NAPI_RS_WASI_FLAVOR Env Vars: NAPI_RS_WASI_FLAVOR Location: Package overview From: package.json → `npm/vite@8.3.4` → `npm/rolldown@1.2.13` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/rolldown@1.2.13`. 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
	Environment variable access: npm `rolldown` reads NAPI_RS_FORCE_WASI Env Vars: NAPI_RS_FORCE_WASI Location: Package overview From: package.json → `npm/vite@8.3.4` → `npm/rolldown@1.2.13` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/rolldown@1.2.13`. 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
	Environment variable access: npm `rolldown` Location: Package overview From: package.json → `npm/vite@8.3.4` → `npm/rolldown@1.2.13` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/rolldown@1.2.13`. 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
	Environment variable access: npm `rolldown` reads NODE_ENV Env Vars: NODE_ENV Location: Package overview From: package.json → `npm/vite@8.3.4` → `npm/rolldown@1.2.13` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/rolldown@1.2.13`. 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
	Environment variable access: npm `rolldown` reads CONSOLA_LEVEL Env Vars: CONSOLA_LEVEL Location: Package overview From: package.json → `npm/vite@8.3.4` → `npm/rolldown@1.2.13` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/rolldown@1.2.13`. 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
	Environment variable access: npm `rolldown` reads ROLLDOWN_TEST Env Vars: ROLLDOWN_TEST Location: Package overview From: package.json → `npm/vite@8.3.4` → `npm/rolldown@1.2.13` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/rolldown@1.2.13`. 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
	Environment variable access: npm `vitest` reads NODE_ENV Env Vars: NODE_ENV Location: Package overview From: package.json → `npm/vitest@5.0.3` ℹ Read more on: This package \| This alert \| What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/vitest@5.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

Ignoring alerts on:

tinyexec@1.3.1

View full report

cursor

Stale Bugbot comment from a previous run.

…config

mcmire

Thanks for doing this, it's a long time coming. Left some comments below.

mcmire · 2026-10-15T19:06:56Z

Is this file specific to Jest? If so, should we move it to a jest directory to mirror the new vitest directory? Are there any other files we would want to move to jest? (Files that are shared can continue to live directly outside of tests/vitest.)

I did deliberately not move this file, as otherwise the scope of the PR would grow to touch all test files where its imported. I can do this as a follow up PR only dedicated to this.

…g it

## Explanation Groundwork so the Jest to Vitest migration does not have to carry it. Nothing here needs Vitest, each change stands on its own, and the suite still runs on Jest. Deletes slightly more than it adds. * **`buildTestObject` moves to `packages/network-controller/tests/helpers.ts`** and leaves the root `tests/helpers.ts`. That file is its only consumer, and has been since it was written in MetaMask#4286 on 2024-09-03: `git log -S` finds no other package importing it, ever. Its type parameter is `Key` rather than `K` now, which drops an `id-length` suppression instead of carrying it. * **`tests/matchers.ts` holds the matcher implementations**, leaving `tests/setupAfterEnv/matchers.ts` to do only the `expect.extend` registration. That drops two more suppressions. * **`flushPromises` takes `setImmediate` from `node:timers`** instead of `jest.requireActual('timers')`. The same real timer past the fake ones, one fewer unsafe member access on an `any`. * **`types/global.d.ts` is now `types/jest.d.ts`**, since all it holds is `declare namespace jest`. Also drops four suppressions for `packages/seedless-onboarding-controller/src/utils.ts`, a file MetaMask#10568 split into `src/utils/`. They have pointed at nothing since, and oxlint reports them as unused once anything else in the suppressions file moves. ## References * Precedes the Vitest migration stack starting at MetaMask#10546 ## Checklist - [x] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [ ] I've communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) * Not applicable, test only change. Carries the `no-changelog` label. - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them * None.

cursor

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3a2a6d2. Configure here.}

cursor · 2026-10-15T23:00:01Z

    "test": "yarn test:scripts --silent --collectCoverage=false --reporters=jest-silent-reporter && yarn test:scripts:shell && yarn test:packages",
    "test:clean": "yarn workspaces foreach --all --parallel --verbose run test:clean && yarn test",
-    "test:packages": "yarn test:verbose --silent --collectCoverage=false --reporters=jest-silent-reporter",
+    "test:packages": "yarn workspaces foreach --all --parallel --verbose run test --coverage=false",


Root test script recurses infinitely

High Severity

test:packages now runs test across every workspace with --all, and the root test script calls test:packages again. Yarn treats the root as a workspace, so yarn test re-enters itself and never finishes.

^{Reviewed by Cursor Bugbot for commit 3a2a6d2. Configure here.}

cryptodev-2s requested review from a team as code owners September 28, 2026 20:17

cryptodev-2s deployed to default-branch September 28, 2026 20:18 — with GitHub Actions Active

cryptodev-2s added this pull request to stack #10557 September 28, 2026 20:19

cryptodev-2s changed the title ~~test/vitest setup~~ test: add Vitest alongside Jest without migrating any package Sep 28, 2026

cryptodev-2s added the no-changelog label Sep 28, 2026

cursor Bot reviewed Sep 28, 2026

View reviewed changes

Comment thread yarn.config.cjs Outdated

cryptodev-2s force-pushed the test/vitest-setup branch 3 times, most recently from 66adc1a to 7164c57 Compare September 29, 2026 14:38

cryptodev-2s requested a review from a team as a code owner September 29, 2026 14:38

cryptodev-2s removed this pull request from stack #10557 September 29, 2026 14:40

cryptodev-2s changed the base branch from main to test/approval-controller-assert-error-codes September 29, 2026 14:40

cryptodev-2s added this pull request to stack #10578 September 29, 2026 14:41

cryptodev-2s force-pushed the test/vitest-setup branch from 7164c57 to 70edc7c Compare September 30, 2026 07:04

cryptodev-2s force-pushed the test/approval-controller-assert-error-codes branch from c812b32 to bb0a88a Compare September 30, 2026 07:04

cryptodev-2s force-pushed the test/vitest-setup branch from 70edc7c to 83d2d8b Compare October 5, 2026 10:48

cryptodev-2s changed the title ~~test: add Vitest alongside Jest without migrating any package~~ test: add Vitest alongside Jest Oct 15, 2026

test: match Vitest's matcher type parameters and simplify the runner …

a34b583

…config

mcmire reviewed Oct 15, 2026

View reviewed changes

cryptodev-2s mentioned this pull request Oct 15, 2026

test: run the package template on Vitest so generated packages do too #10853

Open

2 of 4 tasks

cryptodev-2s added 13 commits October 15, 2026 22:54

test: drop a gitignore rule that matches nothing

f1cf436

test: except test-runners.cjs in the lint config instead of suppressing

cdf2aff

test: disable the rule in the Vitest setup file instead of suppressin…

d337cfb

…g it

test: drop the Vitest config header comment

e5d56b6

test: trim the matcher type parameter comment

0b4702f

test: separate the two notes in the Vitest matcher types

731771d

test: explain the duplicated helper in checkable terms

b4c415c

test: build the Jest holdout Set without an import alias

f588a6f

test: export the Jest holdouts as a Set

9868bb7

test: derive the per runner package lists in the shared module

83bf943

test: drop the Vitest helpers header comment

abdf4bc

test: rename test-runners.cjs to test-runner-package-map.cjs

38021c0

test: take workspace locations from the workspaces field

476bdf4

cryptodev-2s added 6 commits October 15, 2026 23:59

test: use getWorkspaceLocations from @metamask/action-utils

eb90e95

test: align the shared Vitest config with the monorepo template

c81b06f

test: drop the redundant test-file coverage exclusion

1b06f05

test: trim the comments on the shared Vitest config

810dc4e

test: restore the template wording on unchanged options

908d779

test: disable coverage with a runner argument instead of an env var

c62bb9b

cryptodev-2s requested a review from mcmire October 15, 2026 22:38

cryptodev-2s added 3 commits October 16, 2026 00:43

test: drop comment-only changes outside the Vitest setup

1ae135f

test: trim the comments on the test runner package map

e7f2798

Merge remote-tracking branch 'origin/main' into test/vitest-setup

3a2a6d2

cryptodev-2s self-assigned this Oct 15, 2026

cursor Bot reviewed Oct 15, 2026

View reviewed changes

Conversation

cryptodev-2s commented Sep 28, 2026 • edited by cursor Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation

References

Checklist

Uh oh!

socket-security Bot commented Sep 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented Sep 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cursor Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

mcmire left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

mcmire Oct 15, 2026

Choose a reason for hiding this comment

Uh oh!

cryptodev-2s Oct 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor Bot Oct 15, 2026

Choose a reason for hiding this comment

Root test script recurses infinitely

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

cryptodev-2s commented Sep 28, 2026 •

edited by cursor Bot

Loading

socket-security Bot commented Sep 28, 2026 •

edited

Loading

socket-security Bot commented Sep 28, 2026 •

edited

Loading

cursor Bot left a comment •

edited

Loading

cryptodev-2s Oct 15, 2026 •

edited

Loading