Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency @types/node to v20.17.4 #1014

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 23, 2024

This PR contains the following updates:

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

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.

Copy link

socket-security bot commented Oct 23, 2024

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↗︎

Copy link

socket-security bot commented Oct 23, 2024

🚨 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 NoteSourceCI
Filesystem access npm/[email protected] 🚫
Filesystem access npm/[email protected] 🚫
Shell access npm/[email protected] 🚫
Filesystem access npm/[email protected] 🚫
Uses eval npm/@nicolo-ribaudo/[email protected] 🚫
Uses eval npm/@nicolo-ribaudo/[email protected] 🚫
Uses eval npm/@nicolo-ribaudo/[email protected] 🚫
Uses eval npm/@nicolo-ribaudo/[email protected] 🚫
Uses eval npm/@nicolo-ribaudo/[email protected] 🚫
Uses eval npm/@nicolo-ribaudo/[email protected] 🚫
Uses eval npm/@nicolo-ribaudo/[email protected] 🚫
Uses eval npm/@nicolo-ribaudo/[email protected] 🚫
Uses eval npm/@nicolo-ribaudo/[email protected] 🚫
Filesystem access npm/@nicolo-ribaudo/[email protected] 🚫
Uses eval npm/@nicolo-ribaudo/[email protected] 🚫
Filesystem access npm/[email protected] 🚫
Filesystem access npm/[email protected] 🚫
Environment variable access npm/[email protected] 🚫
Environment variable access npm/[email protected] 🚫
Filesystem access npm/[email protected] 🚫
Environment variable access npm/[email protected] 🚫
Debug access npm/@babel/[email protected] 🚫
Environment variable access npm/@babel/[email protected] 🚫
Environment variable access npm/@babel/[email protected] 🚫
Environment variable access npm/[email protected] 🚫
Debug access npm/@babel/[email protected] 🚫
Environment variable access npm/[email protected] 🚫

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

@renovate renovate bot changed the title Update dependency @types/node to v20.16.15 Update dependency @types/node to v20.17.0 Oct 23, 2024
@renovate renovate bot changed the title Update dependency @types/node to v20.17.0 Update dependency @types/node to v20.17.1 Oct 25, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from da200cd to 42b7b1c Compare October 28, 2024 22:33
@renovate renovate bot changed the title Update dependency @types/node to v20.17.1 Update dependency @types/node to v20.17.2 Oct 28, 2024
@renovate renovate bot changed the title Update dependency @types/node to v20.17.2 Update dependency @types/node to v20.17.3 Oct 29, 2024
@renovate renovate bot changed the title Update dependency @types/node to v20.17.3 Update dependency @types/node to v20.17.4 Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants