Add adapter support for newer chrome versions

[bhackett1024]

https://nut-issue-tracker.netlify.app/issue/ISS-652

[changeset-bot]

⚠️ No Changeset found

Latest commit: aed04f9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	puppeteer-core@​24.39.1

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. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Potential code anomaly (AI signal): npm @puppeteer/browsers is 100.0% likely to have a medium risk anomaly Notes: This code implements multi-format archive extraction via host tools and libraries. It does not appear to contain explicit malicious behavior like network exfiltration, backdoors, or data theft. The primary security considerations are the reliance on external system utilities (which can be misused if the inputs are untrusted) and ensuring proper validation of inputs and safe extraction. Given its purpose within a build/dependency context, the risk is moderate and largely depends on the trustworthiness of the archives being unpacked and the host environment. Confidence: 1.00 Severity: 0.60 From: ? → npm/puppeteer-core@24.39.1 → npm/@puppeteer/browsers@2.13.0 ℹ 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/@puppeteer/browsers@2.13.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		Potential code anomaly (AI signal): npm chromium-bidi is 100.0% likely to have a medium risk anomaly Notes: The analyzed ChannelProxy.js implements a cross-context message channel used by the BiDi protocol to propagate messages from a realm to a user-facing BiDi session. There is no evidence of data exfiltration, reverse shells, or hard-coded secrets. The dynamic evaluation and cross-context delegation are legitimate for its purpose but represent powerful capabilities that, if misused by a downstream attacker or in a compromised runtime, could enable covert data movement. Within the scope of this file alone, the behavior appears to be controlled and purpose-built for inter-context communication rather than malicious activity. Confidence: 1.00 Severity: 0.60 From: ? → npm/puppeteer-core@24.39.1 → npm/chromium-bidi@14.0.0 ℹ 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/chromium-bidi@14.0.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		Potential code anomaly (AI signal): npm puppeteer-core is 100.0% likely to have a medium risk anomaly Notes: The ScriptInjector provides a legitimate extensibility pattern by allowing runtime modification of module.exports.default through externally supplied statements. However, its design enables arbitrary code execution if untrusted input is appended and the injector executes the resulting string. This represents a clear security risk that requires input validation, sandboxed execution, or strict access controls to ensure only trusted amendments are applied. Prefer safer integration patterns or enforce a sandboxed eval/VM environment for any dynamic code evaluation. Confidence: 1.00 Severity: 0.60 From: tests/chrome-test/package.json → npm/puppeteer-core@24.39.1 ℹ 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/puppeteer-core@24.39.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		Potential code anomaly (AI signal): npm zod is 100.0% likely to have a medium risk anomaly Notes: No explicit network exfiltration, reverse shell, or credential theft is present in this fragment. However, the code assembles and compiles arbitrary code via the Function constructor and invokes passed-in functions immediately (twice). That behavior constitutes a strong dangerous primitive (arbitrary code execution) which can be abused if any inputs (strings or args) are attacker-controlled. Treat this module as risky in threat models where inputs are not fully trusted; review call sites and sanitize/validate inputs or avoid dynamic evaluation. Confidence: 1.00 Severity: 0.60 From: ? → npm/puppeteer-core@24.39.1 → npm/zod@3.25.76 ℹ 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/zod@3.25.76. 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