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 eslint-plugin-import to v2.30.0 #993

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 3, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-import 2.29.1 -> 2.30.0 age adoption passing confidence

Release Notes

import-js/eslint-plugin-import (eslint-plugin-import)

v2.30.0

Compare Source

Added
Fixed
Changed
  • [Docs] no-extraneous-dependencies: Make glob pattern description more explicit ([#​2944], thanks [@​mulztob])
  • [no-unused-modules]: add console message to help debug [#​2866]
  • [Refactor] ExportMap: make procedures static instead of monkeypatching exportmap ([#​2982], thanks [@​soryy708])
  • [Refactor] ExportMap: separate ExportMap instance from its builder logic ([#​2985], thanks [@​soryy708])
  • [Docs] order: Add a quick note on how unbound imports and --fix ([#​2640], thanks [@​minervabot])
  • [Tests] appveyor -> GHA (run tests on Windows in both pwsh and WSL + Ubuntu) ([#​2987], thanks [@​joeyguerra])
  • [actions] migrate OSX tests to GHA ([ljharb#37], thanks [@​aks-])
  • [Refactor] exportMapBuilder: avoid hoisting ([#​2989], thanks [@​soryy708])
  • [Refactor] ExportMap: extract "builder" logic to separate files ([#​2991], thanks [@​soryy708])
  • [Docs] [order]: update the description of the pathGroupsExcludedImportTypes option ([#​3036], thanks [@​liby])
  • [readme] Clarify how to install the plugin ([#​2993], thanks [@​jwbth])

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 this update 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 Sep 3, 2024

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

Package New capabilities Transitives Size Publisher
npm/@babel/cli@7.25.6 Transitive: environment, eval, filesystem, network, shell +10 1.41 MB nicolo-ribaudo
npm/@babel/core@7.25.2 environment, filesystem, unsafe +25 10.6 MB nicolo-ribaudo
npm/@babel/preset-env@7.25.4 Transitive: environment, filesystem, unsafe +103 16.4 MB existentialism, hzoo, jlhwung, ...1 more
npm/@types/jest@29.5.12 None 0 78.7 kB types
npm/@types/node@20.16.4 None 0 2.18 MB types
npm/eslint-plugin-import@2.30.0 environment, filesystem, unsafe Transitive: eval +96 6.16 MB ljharb

🚮 Removed packages: npm/eslint-plugin-import@2.29.1

View full report↗︎

Copy link

socket-security bot commented Sep 3, 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
Shell access npm/commander@6.2.1 🚫
Filesystem access npm/commander@6.2.1 🚫
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 🚫
Uses eval npm/@nicolo-ribaudo/chokidar-2@2.1.8-no-fsevents.3 🚫
Filesystem access npm/fs-readdir-recursive@1.1.0 🚫
Filesystem access npm/chokidar@3.6.0 🚫
Environment variable access npm/chokidar@3.6.0 🚫
Environment variable access npm/chokidar@3.6.0 🚫
Filesystem access npm/chokidar@3.6.0 🚫
Environment variable access npm/chokidar@3.6.0 🚫
Debug access npm/@babel/helper-define-polyfill-provider@0.6.2 🚫
Environment variable access npm/@babel/code-frame@7.24.7 🚫
Environment variable access npm/@babel/highlight@7.24.7 🚫
Debug access npm/@babel/core@7.25.2 🚫
Environment variable access npm/browserslist@4.23.3 🚫
Environment variable access npm/eslint-plugin-import@2.30.0 🚫

View full report↗︎

Next steps

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 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 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 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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/commander@6.2.1
  • @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/chokidar@3.6.0
  • @SocketSecurity ignore npm/@babel/helper-define-polyfill-provider@0.6.2
  • @SocketSecurity ignore npm/@babel/code-frame@7.24.7
  • @SocketSecurity ignore npm/@babel/highlight@7.24.7
  • @SocketSecurity ignore npm/@babel/core@7.25.2
  • @SocketSecurity ignore npm/browserslist@4.23.3
  • @SocketSecurity ignore npm/eslint-plugin-import@2.30.0

@renovate renovate bot force-pushed the renovate/eslint-plugin-import-2.x branch 5 times, most recently from 7dce8ad to f65753f Compare September 9, 2024 18:21
@renovate renovate bot force-pushed the renovate/eslint-plugin-import-2.x branch from f65753f to b1dc2e2 Compare September 12, 2024 13:10
@renovate renovate bot force-pushed the renovate/eslint-plugin-import-2.x branch from b1dc2e2 to ea0228c Compare September 12, 2024 23:05
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