Skip to content

Update lockfile #5615

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

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

Update lockfile #5615

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 1, 2025

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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

changeset-bot bot commented Apr 1, 2025

⚠️ No Changeset found

Latest commit: fff57ea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

socket-security bot commented Apr 1, 2025

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

Package New capabilities Transitives Size Publisher
npm/@changesets/[email protected]0.5.1 Transitive: environment, filesystem, network +8 662 kB andarist, changesets-release-bot, emmatown, ...1 more
npm/@changesets/[email protected]2.28.1 Transitive: eval, unsafe +88 15.5 MB andarist, changesets-release-bot, emmatown, ...1 more
npm/@changesets/[email protected], 2.0.02.0.2 Transitive: eval +44 2.41 MB changesets-release-bot
npm/@changesets/[email protected], 0.6.00.6.3 Transitive: eval, shell +61 2.68 MB changesets-release-bot
npm/@eslint/[email protected]1.2.8 None 0 48.9 kB eslintbot
npm/@nomicfoundation/[email protected]2.0.8 None +9 520 kB schaable
npm/@nomicfoundation/[email protected]3.0.8 Transitive: environment +3 333 kB kanej
npm/@nomicfoundation/[email protected]1.0.12 Transitive: environment, filesystem +41 6.09 MB schaable
npm/@openzeppelin/[email protected]1.0.8 Transitive: environment, network +28 9.6 MB amxx
npm/@openzeppelin/[email protected]0.3.33 Transitive: environment, eval, unsafe +11 3.64 MB amxx
npm/@openzeppelin/[email protected]1.42.2 Transitive: environment +62 13.9 MB amxx, arr00, ericglau, ...3 more
npm/[email protected]4.5.0 None +7 910 kB chaijs
npm/[email protected]10.1.1 None 0 58.4 kB jounqin
npm/[email protected]9.23.0 Transitive: eval, filesystem, shell, unsafe +85 10.1 MB eslintbot
npm/[email protected]6.13.5 Transitive: environment +8 18.5 MB ricmoo
npm/[email protected], 7.2.011.0.1 Transitive: environment, shell +32 3.39 MB isaacs
npm/[email protected]0.3.19 None 0 147 kB frangio
npm/[email protected]2.2.2 Transitive: eval, network, shell, unsafe +106 30.4 MB cgewecke
npm/[email protected]0.2.12 Transitive: filesystem +16 3.78 MB frangio
npm/[email protected]2.22.19 Transitive: eval, unsafe +229 173 MB kanej
npm/[email protected]15.5.0 Transitive: environment, filesystem, shell +45 1.87 MB
npm/[email protected], 6.0.06.2.0 None +1 18.4 kB sindresorhus
npm/[email protected]1.4.2 Transitive: unsafe +1 7.44 MB janther
npm/[email protected]3.5.3 None 0 0 B
npm/[email protected]6.0.1 None +1 318 kB isaacs
npm/[email protected]7.7.1 None 0 96.7 kB npm-cli-ops
npm/[email protected]5.0.5 Transitive: environment, eval, network, shell, unsafe +89 14.2 MB diego.bale.arg
npm/[email protected]0.4.60 None 0 240 kB frangio
npm/[email protected]0.8.14 environment Transitive: eval, network, unsafe +184 26.2 MB cgewecke
npm/[email protected], 7.4.07.7.0 None 0 0 B

View full report↗︎

Copy link

socket-security bot commented Apr 1, 2025

🚨 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
AI-detected potential code anomaly pypi/[email protected]
  • Notes: The code contains multiple potential security risks, including unauthorized file writes, command injection, information leakage, and code injection. It should be reviewed and modified to ensure proper input validation, sanitization, and secure handling of user input. The presence of 'eval' raises concerns about the safety and security of the code.
  • Confidence: 0.80
  • Severity: 0.70
🚫

View full report↗︎

Next steps

What is an AI-detected potential code anomaly?

AI has identified unusual behaviors that may pose a security risk.

An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

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 force-pushed the renovate/lock-file-maintenance branch from bf7ceef to fff57ea Compare April 3, 2025 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants