Update dependency @types/node to v20.13.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	20.12.8 -> 20.13.0

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@types/[email protected]	None	0	40.3 kB	types
npm/@types/[email protected]	None	0	5.75 kB	types
npm/@types/[email protected]	None	+1	779 kB	types
npm/@typescript-eslint/[email protected]	Transitive: environment, filesystem	+27	6.32 MB	jameshenry
npm/@typescript-eslint/[email protected]	Transitive: environment, filesystem	+21	2.44 MB	jameshenry
npm/[email protected]	None	+3	55.6 kB	sindresorhus
npm/[email protected]	Transitive: environment, eval, filesystem, network	+20	2.98 MB	loganfsmyth
npm/[email protected]	Transitive: environment, eval, filesystem, network	+64	5.7 MB	existentialism
npm/[email protected]	None	+2	46.3 kB	ljharb
npm/[email protected]	None	+8	2.32 MB	ljharb
npm/[email protected]	filesystem Transitive: environment	+10	144 kB	isaacs
npm/[email protected]	None	0	17.6 kB	ljharb
npm/[email protected]	None	0	229 kB	jordanbtucker
npm/[email protected]	None	0	1.41 MB	bnjmnt4n
npm/[email protected]	None	0	7 kB	yeikos
npm/[email protected]	None	0	8.9 kB	zensh
npm/[email protected]	None	0	97.2 kB	ljharb
npm/[email protected]	None	+1	57.9 kB	gkz
npm/[email protected]	None	+6	101 kB	ljharb

🚮 Removed packages: npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

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
Environment variable access	npm/[email protected]	Env Vars: DEBUG_FD Location: Package overview	javascript/etl/package-lock.json javascript/etl/package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	javascript/etl/package-lock.json javascript/etl/package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	typescript/two-fer/package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	typescript/two-fer/package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	Source
Environment variable access	npm/[email protected]	Env Vars: Location: Package overview	javascript/etl/package-lock.json javascript/etl/package.json
Environment variable access	npm/[email protected]	Env Vars: Location: Package overview	typescript/two-fer/package.json
Environment variable access	npm/[email protected]	Env Vars: MINIMATCH_TESTING_PLATFORM Location: Package overview	typescript/two-fer/package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	typescript/two-fer/package.json
CVE	npm/[email protected]	CVE: GHSA-9c47-m6qq-7p4h Prototype Pollution in JSON5 via Parse Method (HIGH) Affected versions: >= 2.0.0, < 2.2.2 Patched version: 2.2.2	Source
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	typescript/two-fer/package.json
Critical CVE	npm/[email protected]	CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: No patched versions	javascript/etl/package-lock.json javascript/etl/package.json
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	javascript/etl/package-lock.json javascript/etl/package.json
Deprecated	npm/[email protected]	Reason: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.	javascript/etl/package-lock.json javascript/etl/package.json
Uses eval	npm/[email protected]	Eval Type: Function Location: Package overview	javascript/etl/package-lock.json javascript/etl/package.json
Uses eval	npm/[email protected]	Eval Type: Function Location: Package overview	javascript/etl/package-lock.json javascript/etl/package.json
Environment variable access	npm/[email protected]	Env Vars: key Location: Package overview	typescript/two-fer/package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	typescript/two-fer/package.json
Debug access	npm/[email protected]	Module: module Location: Package overview	typescript/two-fer/package.json

View full report↗︎

Next steps

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 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 a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

What is eval?

Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use eval, since this could potentially execute any code.

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/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]