Skip to content

[EMBED-591] tkey stack upgrade 2026 Q4 - #319

Draft
lionellbriones wants to merge 7 commits into
masterfrom
feat/embed-591-stack-upgrade
Draft

lionellbriones wants to merge 7 commits into
masterfrom
feat/embed-591-stack-upgrade

Conversation

@lionellbriones

@lionellbriones lionellbriones commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Motivation and Context

Modernize the tkey monorepo to the 2026 Q4 stack policy: Node, npm, LavaMoat, TypeScript, Oxlint/Oxfmt, Vite+ library builds, and Changesets.

This is a breaking change for published packages. Engines are Node >=24.22.0 and npm >=12. types is dist/lib.cjs/index.d.ts. The unused @babel/runtime peer dependency and the UMD build are gone.

Release-adoption gates still have no newer major:

  • @toruslabs/customauth stays ^22.3.3 (EMBED-590)
  • @toruslabs/torus.js stays ^17.2.3 (EMBED-588)

Majors adopted on this branch:

  • @toruslabs/fetch-node-details 17
  • @toruslabs/metadata-helpers 9
  • @toruslabs/eccrypto 8
  • @toruslabs/http-helpers 10
  • @toruslabs/constants 17
  • typescript 7, @toruslabs/config 5, @toruslabs/torus-scripts 9.0.1
  • @types/node 26
  • vite-plus 1.5.1, which pins vitest and @vitest/browser-playwright at 5.1.0

Jira Link

Description

Each published package now uses:

  • main: dist/lib.cjs/index.js
  • module, unpkg, and jsdelivr: dist/lib.esm/index.js
  • types: dist/lib.cjs/index.d.ts

There is no exports map and no UMD file. A packed @tkey/common-types tarball loads ShareStore and bigIntReplacer through both require and import. @tkey/chrome-storage resolves the same two entry files; loading it in Node then throws from webextension-polyfill, which only runs inside an extension.

CI is validate on pull requests and master for Node 24.22.0 and 26, plus a manual release-pr workflow that opens the release pull request and does not publish. security-code-scanner runs on pull requests, pushes to master, a weekly cron, and manual dispatch. No second CodeQL workflow was added. KICS, Trivy, AWS credentials, and a Wiz sensor do not apply: this repository has no backend, container, or deploy. The token cannot read or change the repository setting that lets Actions open pull requests, or the CodeQL default setup (HTTP 403).

npm audit on this branch reports 15 findings (8 low, 7 moderate). The critical and high findings were updated in range. Still open:

  • deepmerge 4.3.1 (GHSA-gcqx-w48m-w2h4) is the latest 4.x and is still affected. The vulnerable copy is nested under CustomAuth 22 and torus.js 17. The audit fix would downgrade CustomAuth to 18.1.0.
  • minimatch below 11.0.1 (GHSA-g3hv-75wg-m249) is required at ^10.2 by ESLint and the Oxlint preset's eslint-plugin-tsdoc. Forcing 11 would cross that major. This is lint tooling.

Dependabot on the default branch still reports 143 findings until this branch merges. Those alerts were not dismissed.

Nothing has been published. release-packages stays manual on master after the release pull request merges.

How has this been tested?

  • Clean install, check, build, and typecheck on Node 24.22.1 and Node 26.13.0. CI pins Node 24.22.0; 24.22.0 was not installed locally.
  • Mocked repository tests on both Node versions. @tkey/default passed 55 tests and skipped 4. Eleven seed-phrase tests fail locally because TEST_RPC_TARGET is unset. A public Cloudflare endpoint returned RPC internal errors, so those tests still need the GitHub secret.
  • web-storage mocked Chrome browser tests: 12 passed.
  • chrome-storage has no test files. Its packed entry was loaded in Node only.
  • Service-backed test-production, the TKEY_FULL=1 suite, and non-mocked OneKey tests. They need TEST_RPC_TARGET and the live metadata service.
  • Default package browser matrix (Chrome, Firefox, and Safari).
  • Packed tarball require and import for @tkey/common-types.
  • External tkey/backward-compatibility-tests repository.
  • Tag-triggered mock generation. That workflow pushes to another repository, so it was not dispatched.

Screenshots (if appropriate)

No UI changes.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

  • My code follows the code style of this project. (run lint)
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

lionellbriones and others added 2 commits November 10, 2026 13:23
Co-authored-by: Cursor <cursoragent@cursor.com>
…rus.js.

Co-authored-by: Cursor <cursoragent@cursor.com>
@socket-security

socket-security Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

Lerna and torus-scripts 8 cannot emit the existing dist layout or typecheck under the new TypeScript and Oxlint presets.

Co-authored-by: Cursor <cursoragent@cursor.com>
@socket-security

socket-security Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

Caution

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
Medium priority
Publisher changed: npm @toruslabs/fetch-node-details is now published by archit_web3

Author: archit_web3

From: package-lock.json → npm/@toruslabs/customauth@22.3.3 → npm/@toruslabs/fetch-node-details@16.1.1

ℹ Read more on: This package | This alert | What is unstable ownership?

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: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@toruslabs/fetch-node-details@16.1.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.

Block
Medium priority
Publisher changed: npm @toruslabs/fnd-base is now published by archit_web3

Author: archit_web3

From: package-lock.json → npm/@toruslabs/customauth@22.3.3 → npm/@toruslabs/fnd-base@16.1.1

ℹ Read more on: This package | This alert | What is unstable ownership?

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: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@toruslabs/fnd-base@16.1.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.

Block
Low priority
Publisher changed: npm @toruslabs/constants is now published by archit_web3 instead of chaitanyapotti

New Author: archit_web3

Previous Author: chaitanyapotti

From: package-lock.json → npm/@toruslabs/torus.js@17.2.3 → npm/@toruslabs/customauth@22.3.3 → npm/@toruslabs/constants@16.1.1

ℹ Read more on: This package | This alert | What is new author?

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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@toruslabs/constants@16.1.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.

Block
Low priority
Publisher changed: npm @toruslabs/fetch-node-details is now published by archit_web3 instead of chaitanyapotti

New Author: archit_web3

Previous Author: chaitanyapotti

From: package-lock.json → npm/@toruslabs/customauth@22.3.3 → npm/@toruslabs/fetch-node-details@16.1.1

ℹ Read more on: This package | This alert | What is new author?

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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@toruslabs/fetch-node-details@16.1.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.

Block
Low priority
Publisher changed: npm @toruslabs/fnd-base is now published by archit_web3 instead of chaitanyapotti

New Author: archit_web3

Previous Author: chaitanyapotti

From: package-lock.json → npm/@toruslabs/customauth@22.3.3 → npm/@toruslabs/fnd-base@16.1.1

ℹ Read more on: This package | This alert | What is new author?

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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@toruslabs/fnd-base@16.1.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.

Block
Low priority
Network access: npm @vitest/browser-playwright in module globalThis["fetch"]

Module: globalThis["fetch"]

Location: Package overview

From: package-lock.json → npm/@vitest/browser-playwright@5.1.0

ℹ 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/browser-playwright@5.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.

Warn
Low priority
Network access: npm @yarnpkg/core in module https

Module: https

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/@yarnpkg/core@4.8.0

ℹ 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/@yarnpkg/core@4.8.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
Low priority
Network access: npm @yarnpkg/core in module http

Module: http

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/@yarnpkg/core@4.8.0

ℹ 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/@yarnpkg/core@4.8.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
Low priority
Network access: npm @yarnpkg/core in module globalThis["fetch"]

Module: globalThis["fetch"]

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/@yarnpkg/core@4.8.0

ℹ 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/@yarnpkg/core@4.8.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
Low priority
Network access: npm cacheable-lookup in module dns

Module: dns

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/cacheable-lookup@5.0.4

ℹ 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/cacheable-lookup@5.0.4. 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
Low priority
Network access: npm hpagent in module https

Module: https

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/hpagent@1.2.0

ℹ 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/hpagent@1.2.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
Low priority
Network access: npm hpagent in module http

Module: http

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/hpagent@1.2.0

ℹ 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/hpagent@1.2.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
Low priority
Network access: npm http2-wrapper in module tls

Module: tls

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/http2-wrapper@1.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/http2-wrapper@1.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
Low priority
Network access: npm http2-wrapper in module http2

Module: http2

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/http2-wrapper@1.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/http2-wrapper@1.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
Low priority
Network access: npm http2-wrapper in module http

Module: http

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/http2-wrapper@1.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/http2-wrapper@1.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
Low priority
Network access: npm http2-wrapper in module https

Module: https

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/http2-wrapper@1.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/http2-wrapper@1.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
Low priority
Network access: npm http2-wrapper in module net

Module: net

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/http2-wrapper@1.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/http2-wrapper@1.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
Low priority
Network access: npm resolve-alpn in module tls

Module: tls

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/resolve-alpn@1.2.1

ℹ 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/resolve-alpn@1.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
Low priority
Network access: npm vitest in module globalThis["fetch"]

Module: globalThis["fetch"]

Location: Package overview

From: package-lock.json → npm/@vitest/browser-playwright@5.1.0 → npm/@vitest/coverage-istanbul@5.1.0 → npm/vite-plus@1.5.1 → npm/vitest@5.1.0

ℹ 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.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.

Warn
Low priority
Potential code anomaly (AI signal): npm ws is 75.0% likely to have a medium risk anomaly

Notes: The code implements a standard EventTarget-like mixin for wrapping event listeners and dispatching events to user callbacks. There are no suspicious patterns such as dynamic code execution, hardcoded secrets, or network activity. The risk is contingent on what the consumer does inside their handlers; the snippet itself does not introduce malware or data leakage mechanisms beyond normal event dispatch. Overall security risk is low in isolation.

Confidence: 0.75

Severity: 0.50

From: package-lock.json → npm/@toruslabs/customauth@22.3.3 → npm/ws@8.21.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/ws@8.21.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
Low priority
Network access: npm @voidzero-dev/vite-plus-core in module globalThis["fetch"]

Module: globalThis["fetch"]

Location: Package overview

From: package-lock.json → npm/@vitest/browser-playwright@5.1.0 → npm/@vitest/coverage-istanbul@5.1.0 → npm/vite-plus@1.5.1 → npm/@voidzero-dev/vite-plus-core@1.5.1

ℹ 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/@voidzero-dev/vite-plus-core@1.5.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
Low priority
Network access: npm got in module http

Module: http

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/got@11.8.6

ℹ 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/got@11.8.6. 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
Low priority
Network access: npm got in module https

Module: https

Location: Package overview

From: package-lock.json → npm/@lavamoat/harden@0.8.1 → npm/got@11.8.6

ℹ 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/got@11.8.6. 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
See 65 more rows in the dashboard

Ignoring alerts on:

  • @changesets/cli@2.31.1
  • @lavamoat/harden@0.8.1
  • @oxfmt/binding-openharmony-arm64@0.76.0
  • @oxlint/binding-darwin-arm64@1.91.0
  • @oxlint/binding-darwin-x64@1.91.0
  • @oxlint/binding-linux-riscv64-musl@1.91.0
  • @typescript/typescript-aix-ppc64@7.0.2
  • @typescript/typescript-darwin-arm64@7.0.2
  • @typescript/typescript-darwin-x64@7.0.2
  • @typescript/typescript-freebsd-arm64@7.0.2
  • @typescript/typescript-freebsd-x64@7.0.2
  • @typescript/typescript-linux-arm@7.0.2
  • @typescript/typescript-linux-arm64@7.0.2
  • @typescript/typescript-linux-loong64@7.0.2
  • @typescript/typescript-linux-mips64el@7.0.2
  • @typescript/typescript-linux-ppc64@7.0.2
  • @typescript/typescript-linux-riscv64@7.0.2
  • @typescript/typescript-linux-s390x@7.0.2
  • @typescript/typescript-linux-x64@7.0.2
  • @typescript/typescript-netbsd-arm64@7.0.2
  • @typescript/typescript-netbsd-x64@7.0.2
  • @typescript/typescript-openbsd-arm64@7.0.2
  • @typescript/typescript-openbsd-x64@7.0.2
  • @typescript/typescript-sunos-x64@7.0.2
  • @typescript/typescript-win32-arm64@7.0.2
  • @typescript/typescript-win32-x64@7.0.2
  • @voidzero-dev/vite-plus-darwin-x64@1.5.1
  • clone-response@1.0.3
  • oxfmt@0.76.0
  • responselike@2.0.1
  • term-size@2.2.1
  • tinypool@2.2.0
  • yuku-core@0.19.0
  • typescript@7.0.2
  • eslint-plugin-tsdoc@0.5.4
  • playwright-core@1.65.0
  • tinyexec@1.3.1
  • tslib@2.9.1

View full report

…kflows.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

Comment on lines +13 to +38
runs-on: ubuntu-latest

steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

- name: Setup Node.js ${{ env.NODE_VERSION }}
uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
with:
node-version: ${{ env.NODE_VERSION }}
cache: "npm"

- name: Install npm 12
run: npm install --global npm@12.2.0

- name: Install Node.js dependencies
run: npm ci

- name: Run Build
run: npm run build && npm exec -- playwright install --with-deps

- name: Browser tests mocked
run: npm run browser-tests:local-mocked

- name: Browser tests production
run: npm run browser-tests:local-prod
Comment thread packages/core/src/core.ts
this.shares[ss.polynomialID][ss.share.shareIndex.toString(16)] = ss;
const sharesForPoly = this.shares[ss.polynomialID];
if (!sharesForPoly) throw CoreError.fromCode(1307);
sharesForPoly[ss.share.shareIndex.toString(16)] = ss;
if (!sharesForPolynomial) {
throw CoreError.default("there is no matching polyID");
}
sharesForPolynomial[publicShare.shareIndex.toString(16)] = publicShare;
const index = descriptions.indexOf(oldDescription);
if (index > -1) {
currentSD[shareIndex][index] = newDescription;
descriptions[index] = newDescription;
lionellbriones and others added 3 commits November 10, 2026 15:22
…de the 3-day window.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@lionellbriones

Copy link
Copy Markdown
Contributor Author

@SocketSecurity ignore npm/eslint-plugin-tsdoc@0.5.4
@SocketSecurity ignore npm/playwright-core@1.65.0
@SocketSecurity ignore npm/tinyexec@1.3.1
@SocketSecurity ignore npm/tinyexec@1.0.4
@SocketSecurity ignore npm/tslib@2.9.1
@SocketSecurity ignore npm/responselike@2.0.1
@SocketSecurity ignore npm/clone-response@1.0.3
@SocketSecurity ignore npm/term-size@2.2.1
@SocketSecurity ignore npm/@typescript/typescript-linux-arm64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-linux-loong64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-linux-ppc64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-linux-s390x@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-freebsd-arm64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-aix-ppc64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-darwin-x64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-linux-arm@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-linux-riscv64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-freebsd-x64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-linux-mips64el@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-darwin-arm64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-openbsd-x64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-netbsd-arm64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-linux-x64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-sunos-x64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-win32-x64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-win32-arm64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-openbsd-arm64@7.0.2
@SocketSecurity ignore npm/@typescript/typescript-netbsd-x64@7.0.2
@SocketSecurity ignore npm/typescript@7.0.2
@SocketSecurity ignore npm/@changesets/cli@2.31.1
@SocketSecurity ignore npm/tinypool@2.2.0
@SocketSecurity ignore npm/@lavamoat/harden@0.8.1
@SocketSecurity ignore npm/yuku-core@0.19.0
@SocketSecurity ignore npm/@oxfmt/binding-openharmony-arm64@0.76.0
@SocketSecurity ignore npm/oxfmt@0.76.0
@SocketSecurity ignore npm/@oxlint/binding-darwin-arm64@1.91.0
@SocketSecurity ignore npm/@oxlint/binding-linux-riscv64-musl@1.91.0
@SocketSecurity ignore npm/@oxlint/binding-darwin-x64@1.91.0
@SocketSecurity ignore npm/@voidzero-dev/vite-plus-darwin-x64@1.5.1

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.

2 participants