SDK regeneration

[fern-api]

Automated SDK generation by Fern

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​jest-fetch-mock@​3.0.3 ⏵ 3.2.0	-1			+12
	npm/​@​types/​readable-stream@​4.0.23 ⏵ 4.0.24	+1		+1	+7
	npm/​webpack@​5.105.4 ⏵ 5.109.1				+1
	npm/​form-data@​4.0.5 ⏵ 4.0.6	+1	+16	+1
	npm/​ts-loader@​9.5.4 ⏵ 9.6.2	+1			-1
	npm/​ts-jest@​29.4.6 ⏵ 29.4.12			+1	+3

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Recently published: npm @types/node published 21 hours ago Location: Package overview From: yarn.lock → npm/@types/readable-stream@4.0.24 → npm/webpack@5.109.1 → npm/@types/jest@29.5.14 → npm/jest-environment-jsdom@29.7.0 → npm/@jest/globals@29.7.0 → npm/@types/node-fetch@2.6.13 → npm/jest@29.7.0 → npm/@types/node@26.1.2 ℹ Read more on: This package | This alert | What are recently published artifacts? 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 either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@types/node@26.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: npm acorn published 8 hours ago Location: Package overview From: yarn.lock → npm/webpack@5.109.1 → npm/jest-environment-jsdom@29.7.0 → npm/acorn@8.18.0 ℹ Read more on: This package | This alert | What are recently published artifacts? 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 either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/acorn@8.18.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.
Block		Recently published: npm baseline-browser-mapping published 22 hours ago Location: Package overview From: yarn.lock → npm/webpack@5.109.1 → npm/@jest/globals@29.7.0 → npm/jest@29.7.0 → npm/baseline-browser-mapping@2.11.5 ℹ Read more on: This package | This alert | What are recently published artifacts? 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 either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/baseline-browser-mapping@2.11.5. 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		Recently published: npm electron-to-chromium published 13 hours ago Location: Package overview From: yarn.lock → npm/webpack@5.109.1 → npm/@jest/globals@29.7.0 → npm/jest@29.7.0 → npm/electron-to-chromium@1.5.397 ℹ Read more on: This package | This alert | What are recently published artifacts? 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 either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/electron-to-chromium@1.5.397. 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		Recently published: npm webpack published 17 hours ago Location: Package overview From: package.json → npm/webpack@5.109.1 ℹ Read more on: This package | This alert | What are recently published artifacts? 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 either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/webpack@5.109.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		License policy violation: npm caniuse-lite under CC-BY-4.0 Location: Package overview From: yarn.lock → npm/webpack@5.109.1 → npm/@jest/globals@29.7.0 → npm/jest@29.7.0 → npm/caniuse-lite@1.0.30001806 ℹ 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.30001806. 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		Obfuscated code: npm webpack is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → npm/webpack@5.109.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/webpack@5.109.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		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: yarn.lock → npm/jest@29.7.0 → npm/msw@2.11.2 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.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		Network access: npm @types/node in module node:dgram Module: node:dgram Location: Package overview From: yarn.lock → npm/@types/readable-stream@4.0.24 → npm/webpack@5.109.1 → npm/@types/jest@29.5.14 → npm/jest-environment-jsdom@29.7.0 → npm/@jest/globals@29.7.0 → npm/@types/node-fetch@2.6.13 → npm/jest@29.7.0 → npm/@types/node@26.1.2 ℹ 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/@types/node@26.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @types/node in module node:net Module: node:net Location: Package overview From: yarn.lock → npm/@types/readable-stream@4.0.24 → npm/webpack@5.109.1 → npm/@types/jest@29.5.14 → npm/jest-environment-jsdom@29.7.0 → npm/@jest/globals@29.7.0 → npm/@types/node-fetch@2.6.13 → npm/jest@29.7.0 → npm/@types/node@26.1.2 ℹ 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/@types/node@26.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @types/node in module node:tls Module: node:tls Location: Package overview From: yarn.lock → npm/@types/readable-stream@4.0.24 → npm/webpack@5.109.1 → npm/@types/jest@29.5.14 → npm/jest-environment-jsdom@29.7.0 → npm/@jest/globals@29.7.0 → npm/@types/node-fetch@2.6.13 → npm/jest@29.7.0 → npm/@types/node@26.1.2 ℹ 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/@types/node@26.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @types/node in module node:dns Module: node:dns Location: Package overview From: yarn.lock → npm/@types/readable-stream@4.0.24 → npm/webpack@5.109.1 → npm/@types/jest@29.5.14 → npm/jest-environment-jsdom@29.7.0 → npm/@jest/globals@29.7.0 → npm/@types/node-fetch@2.6.13 → npm/jest@29.7.0 → npm/@types/node@26.1.2 ℹ 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/@types/node@26.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @types/node in module node:dns/promises Module: node:dns/promises Location: Package overview From: yarn.lock → npm/@types/readable-stream@4.0.24 → npm/webpack@5.109.1 → npm/@types/jest@29.5.14 → npm/jest-environment-jsdom@29.7.0 → npm/@jest/globals@29.7.0 → npm/@types/node-fetch@2.6.13 → npm/jest@29.7.0 → npm/@types/node@26.1.2 ℹ 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/@types/node@26.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @types/node in module node:http Module: node:http Location: Package overview From: yarn.lock → npm/@types/readable-stream@4.0.24 → npm/webpack@5.109.1 → npm/@types/jest@29.5.14 → npm/jest-environment-jsdom@29.7.0 → npm/@jest/globals@29.7.0 → npm/@types/node-fetch@2.6.13 → npm/jest@29.7.0 → npm/@types/node@26.1.2 ℹ 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/@types/node@26.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @types/node in module node:http2 Module: node:http2 Location: Package overview From: yarn.lock → npm/@types/readable-stream@4.0.24 → npm/webpack@5.109.1 → npm/@types/jest@29.5.14 → npm/jest-environment-jsdom@29.7.0 → npm/@jest/globals@29.7.0 → npm/@types/node-fetch@2.6.13 → npm/jest@29.7.0 → npm/@types/node@26.1.2 ℹ 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/@types/node@26.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @types/node in module node:https Module: node:https Location: Package overview From: yarn.lock → npm/@types/readable-stream@4.0.24 → npm/webpack@5.109.1 → npm/@types/jest@29.5.14 → npm/jest-environment-jsdom@29.7.0 → npm/@jest/globals@29.7.0 → npm/@types/node-fetch@2.6.13 → npm/jest@29.7.0 → npm/@types/node@26.1.2 ℹ 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/@types/node@26.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @types/node in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: yarn.lock → npm/@types/readable-stream@4.0.24 → npm/webpack@5.109.1 → npm/@types/jest@29.5.14 → npm/jest-environment-jsdom@29.7.0 → npm/@jest/globals@29.7.0 → npm/@types/node-fetch@2.6.13 → npm/jest@29.7.0 → npm/@types/node@26.1.2 ℹ 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/@types/node@26.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		System shell access: npm @types/node in module node:child_process Module: node:child_process Location: Package overview From: yarn.lock → npm/@types/readable-stream@4.0.24 → npm/webpack@5.109.1 → npm/@types/jest@29.5.14 → npm/jest-environment-jsdom@29.7.0 → npm/@jest/globals@29.7.0 → npm/@types/node-fetch@2.6.13 → npm/jest@29.7.0 → npm/@types/node@26.1.2 ℹ Read more on: This package | This alert | What is shell 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 avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@types/node@26.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Dynamic code execution: npm minimizer-webpack-plugin Eval Type: Function Location: Package overview From: yarn.lock → npm/webpack@5.109.1 → npm/minimizer-webpack-plugin@5.6.1 ℹ Read more on: This package | This alert | What is dynamic code execution? 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: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/minimizer-webpack-plugin@5.6.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.

View full report