Update dependency @types/node to v20.17.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	20.16.14 -> 20.17.4

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@babel/[email protected]	Transitive: environment, eval, filesystem, network, shell	+37	2.13 MB	nicolo-ribaudo
npm/@babel/[email protected]	environment, filesystem, unsafe Transitive: shell	+48	11.3 MB	nicolo-ribaudo
npm/@babel/[email protected]	Transitive: environment, filesystem, shell, unsafe	+152	18.3 MB	existentialism, hzoo, jlhwung, ...1 more
npm/@types/[email protected]	Transitive: environment, filesystem, unsafe	+42	1.67 MB	types
npm/@types/[email protected]	None	+1	2.31 MB	types

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
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Shell access	npm/[email protected]	Module: child_process Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Uses eval	npm/@nicolo-ribaudo/[email protected]	Eval Type: eval Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Uses eval	npm/@nicolo-ribaudo/[email protected]	Eval Type: eval Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Uses eval	npm/@nicolo-ribaudo/[email protected]	Eval Type: eval Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Uses eval	npm/@nicolo-ribaudo/[email protected]	Eval Type: eval Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Uses eval	npm/@nicolo-ribaudo/[email protected]	Eval Type: eval Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Uses eval	npm/@nicolo-ribaudo/[email protected]	Eval Type: eval Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Uses eval	npm/@nicolo-ribaudo/[email protected]	Eval Type: eval Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Uses eval	npm/@nicolo-ribaudo/[email protected]	Eval Type: eval Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Uses eval	npm/@nicolo-ribaudo/[email protected]	Eval Type: eval Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Filesystem access	npm/@nicolo-ribaudo/[email protected]	Module: fs Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Uses eval	npm/@nicolo-ribaudo/[email protected]	Eval Type: eval Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: CHOKIDAR_USEPOLLING Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: CHOKIDAR_INTERVAL Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Filesystem access	npm/[email protected]	Module: fsevents Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: CHOKIDAR_PRINT_FSEVENTS_REQUIRE_ERROR Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Debug access	npm/@babel/[email protected]	Module: module Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Environment variable access	npm/@babel/[email protected]	Env Vars: FORCE_COLOR Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Environment variable access	npm/@babel/[email protected]	Env Vars: FORCE_COLOR Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: HADOOP_HOME Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Debug access	npm/@babel/[email protected]	Module: v8 Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: BROWSERSLIST_ROOT_PATH Location: Package overview	javascript/gigasecond/package-lock.json javascript/gigasecond/package.json	🚫

View full report↗︎

Next steps

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is dynamic code execution?

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is debug access?

Uses debug, reflection and dynamic code execution features.

Removing the use of debug will reduce the risk of any reflection and dynamic code execution.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@nicolo-ribaudo/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@babel/[email protected]
• @SocketSecurity ignore npm/@babel/[email protected]
• @SocketSecurity ignore npm/@babel/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@babel/[email protected]
• @SocketSecurity ignore npm/[email protected]