chore(deps): bump the npm_and_yarn group across 2 directories with 19 updates by dependabot[bot] · Pull Request #950 · thirdweb-dev/engine

Pull Request #950 Alerts: Complete with warnings

Report	Status	Message
PR #950 Alerts	⚠️	Found 1 project alert

Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm `node-forge` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: yarn.lock → `npm/ethers-gcp-kms-signer@1.1.6` → `npm/@cloud-cryptographic-wallet/cloud-kms-signer@0.1.2` → `npm/@thirdweb-dev/auth@4.1.97` → `npm/@thirdweb-dev/sdk@4.0.99` → `npm/thirdweb@5.29.6` → `npm/thirdweb@5.105.42` → `npm/node-forge@1.4.0` ℹ 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/node-forge@1.4.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.