defender-client-deps: bump @types/node from 16.18.97 to 16.18.126

[dependabot]

Bumps @types/node from 16.18.97 to 16.18.126.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: vulnerabilites. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@openzeppelin/defender-admin-client@1.50.0	environment	+1	193 kB	collins-oz
npm/@openzeppelin/defender-admin-client@1.54.2	environment Transitive: network	+49	20.2 MB	tirumerla
npm/@openzeppelin/defender-autotask-client@1.54.2	environment, filesystem	+11	1.96 MB	tirumerla
npm/@openzeppelin/defender-base-client@1.49.0	None	0	86.3 kB	collins-oz
npm/@openzeppelin/defender-relay-client@1.54.6	environment Transitive: eval, filesystem, network	+83	10.3 MB	tirumerla
npm/@openzeppelin/defender-sentinel-client@1.54.6	environment	0	106 kB	tirumerla
npm/@openzeppelin/platform-deploy-client@0.7.0	environment Transitive: network	+2	2.67 MB	namis

🚮 Removed packages: npm/@jest/schemas@29.6.3, npm/@nrwl/tao@16.10.0, npm/@nx/nx-darwin-arm64@16.10.0, npm/@nx/nx-darwin-x64@16.10.0, npm/@nx/nx-freebsd-x64@16.10.0, npm/@nx/nx-linux-arm-gnueabihf@16.10.0, npm/@nx/nx-linux-arm64-gnu@16.10.0, npm/@nx/nx-linux-arm64-musl@16.10.0, npm/@nx/nx-linux-x64-gnu@16.10.0, npm/@nx/nx-linux-x64-musl@16.10.0, npm/@nx/nx-win32-arm64-msvc@16.10.0, npm/@nx/nx-win32-x64-msvc@16.10.0, npm/@parcel/watcher@2.0.4, npm/@yarnpkg/lockfile@1.1.0, npm/@yarnpkg/parsers@3.0.0-rc.46, npm/@zkochan/js-yaml@0.0.6, npm/ansi-colors@4.1.3, npm/ansi-regex@5.0.1, npm/ansi-styles@4.3.0, npm/argparse@2.0.1, npm/axios@1.7.2, npm/balanced-match@1.0.2, npm/bl@4.1.0, npm/brace-expansion@1.1.11, npm/cli-cursor@3.1.0, npm/cli-spinners@2.6.1, npm/cliui@8.0.1, npm/color-convert@2.0.1, npm/concat-map@0.0.1, npm/define-lazy-prop@2.0.0, npm/diff-sequences@29.6.3, npm/dotenv-expand@10.0.0, npm/dotenv@16.3.2, npm/duplexer@0.1.2, npm/emoji-regex@8.0.0, npm/end-of-stream@1.4.4, npm/enquirer@2.3.6, npm/escalade@3.1.2, npm/escape-string-regexp@1.0.5, npm/esprima@4.0.1, npm/figures@3.2.0, npm/flat@5.0.2, npm/follow-redirects@1.15.6, npm/fs-constants@1.0.0, npm/fs-extra@11.2.0, npm/fs.realpath@1.0.0, npm/get-caller-file@2.0.5, npm/graceful-fs@4.2.11, npm/has-flag@4.0.0, npm/ignore@5.3.1, npm/inflight@1.0.6, npm/is-docker@2.2.1, npm/is-fullwidth-code-point@3.0.0, npm/is-wsl@2.2.0, npm/jest-diff@29.7.0, npm/jest-get-type@29.6.3, npm/js-yaml@4.1.0, npm/json5@2.2.3, npm/jsonc-parser@3.2.0, npm/jsonfile@6.1.0, npm/lines-and-columns@2.0.4, npm/lru-cache@6.0.0, npm/minimatch@3.0.5, npm/node-addon-api@3.2.1, npm/node-gyp-build@4.8.1, npm/node-machine-id@1.1.12, npm/npm-run-path@4.0.1, npm/nx@16.10.0, npm/once@1.4.0, npm/onetime@5.1.2, npm/open@8.4.2, npm/path-is-absolute@1.0.1, npm/path-key@3.1.1, npm/pretty-format@29.7.0, npm/react-is@18.3.1, npm/require-directory@2.1.1, npm/restore-cursor@3.1.0, npm/semver@7.5.3, npm/signal-exit@3.0.7, npm/strip-bom@3.0.0, npm/strong-log-transformer@2.1.0, npm/supports-color@7.2.0, npm/tar-stream@2.2.0, npm/through@2.3.8, npm/tmp@0.2.3, npm/tsconfig-paths@4.2.0, npm/universalify@2.0.1, npm/util-deprecate@1.0.2, npm/v8-compile-cache@2.3.0, npm/wrap-ansi@7.0.0, npm/wrappy@1.0.2, npm/y18n@5.0.8, npm/yallist@4.0.0, npm/yargs@17.7.2

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Protestware or potentially unwanted behavior	npm/es5-ext@0.10.64	Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale	examples/create-relayer/package.json	⚠︎
Protestware or potentially unwanted behavior	npm/es5-ext@0.10.64	Note: The script attempts to run a local post-install script, which could potentially contain malicious code. The error handling suggests that it is designed to fail silently, which is a common tactic in malicious scripts.	examples/create-relayer/package.json	⚠︎

View full report↗︎

Next steps

What is protestware?

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Consider that consuming this package may come along with functionality unrelated to its primary purpose.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/es5-ext@0.10.64