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.14.10 #969

Merged
merged 1 commit into from
Jul 11, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 9, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 20.14.9 -> 20.14.10 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 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.

Copy link

socket-security bot commented Jul 9, 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/chokidar@3.5.3 🚫
Environment variable access npm/chokidar@3.5.3 🚫
Environment variable access npm/chokidar@3.5.3 🚫
Filesystem access npm/chokidar@3.5.3 🚫
Environment variable access npm/chokidar@3.5.3 🚫
Filesystem access npm/readdirp@3.6.0 🚫
Deprecated npm/debug@4.1.1 🚫
Mild CVE npm/debug@4.1.1 🚫
Deprecated npm/tslint@6.1.3 🚫
Uses eval npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Uses eval npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Uses eval npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Uses eval npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Uses eval npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Uses eval npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Uses eval npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Uses eval npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Uses eval npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Uses eval npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Filesystem access npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Filesystem access npm/fs-readdir-recursive@1.1.0 🚫
Environment variable access npm/browserslist@4.23.0 🚫
Uses eval npm/core-js@3.37.1 🚫
Uses eval npm/core-js@3.37.1 🚫
Uses eval npm/core-js@3.37.1 🚫
Install scripts npm/core-js@3.37.1
  • Install script: postinstall
  • Source: node -e "try{require('./postinstall')}catch(e){}"
🚫
Filesystem access npm/core-js@3.37.1 🚫
Environment variable access npm/core-js@3.37.1 🚫
Filesystem access npm/@babel/preset-env@7.24.7 🚫
Environment variable access npm/@babel/preset-env@7.24.7 🚫

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

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

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

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 an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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/chokidar@3.5.3
  • @SocketSecurity ignore npm/readdirp@3.6.0
  • @SocketSecurity ignore npm/debug@4.1.1
  • @SocketSecurity ignore npm/tslint@6.1.3
  • @SocketSecurity ignore npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3
  • @SocketSecurity ignore npm/fs-readdir-recursive@1.1.0
  • @SocketSecurity ignore npm/browserslist@4.23.0
  • @SocketSecurity ignore npm/core-js@3.37.1
  • @SocketSecurity ignore npm/@babel/preset-env@7.24.7

@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 6f3294f to 61f7595 Compare July 10, 2024 03:41
@renovate renovate bot merged commit f446a3e into master Jul 11, 2024
6 checks passed
@renovate renovate bot deleted the renovate/node-20.x branch July 11, 2024 01:21
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