Skip to content

fix(deps): update dependency unzipper to ^0.12.5 - #10726

Open
metamask-ci[bot] wants to merge 2 commits into
mainfrom
renovate/zjonsson-node-unzipper
Open

metamask-ci[bot] wants to merge 2 commits into
mainfrom
renovate/zjonsson-node-unzipper

Conversation

@metamask-ci

@metamask-ci metamask-ci Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
unzipper ^0.12.3 → ^0.12.5 age confidence

Release Notes

ZJONSSON/node-unzipper (unzipper)

v0.12.5

Compare Source

v0.12.4

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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.

🔕 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 has been generated by Mend Renovate CLI.

@metamask-ci
metamask-ci Bot requested review from a team as code owners October 7, 2026 19:57
@metamask-ci
metamask-ci Bot temporarily deployed to default-branch October 7, 2026 19:57 Inactive
@socket-security

socket-security Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedunzipper@​0.12.3 ⏵ 0.12.5100 +1100100 +181100

View full report

@socket-security

socket-security Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Warning

MetaMask internal reviewing guidelines:

  • Do not ignore-all
  • Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
  • Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
    @SocketSecurity ignore npm/PACKAGE@VERSION
Priority Alert  (click "▶" to expand/collapse) Action
Low priority
Potential code anomaly (AI signal): npm fs-extra is 78.0% likely to have a medium risk anomaly

Notes: The analyzed code is a standard, legitimate implementation of a recursive copy utility (copySync) from the fs-extra library. It includes typical safeguards (type checks, destination directory creation, overwrite logic, symlink handling, and optional timestamp preservation) and does not exhibit any malicious behavior such as data exfiltration, remote communication, backdoors, or code injection. The warning about preserveTimestamps on ia32 is a benign, user-facing message. Overall security risk is low, with normal filesystem side effects expected. If any concern exists, it would be about untrusted path manipulation via the src/dest, but this is inherent to any filesystem copy utility and mitigated by the provided option hooks (filter, dereference, etc.).

Confidence: 0.78

Severity: 0.50

From: packages/foundryup/package.json → npm/unzipper@0.12.5 → npm/fs-extra@11.3.1

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

Next steps: 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@socket.dev.

Suggestion: 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.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/fs-extra@11.3.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn

View full report

@metamask-ci
metamask-ci Bot force-pushed the renovate/zjonsson-node-unzipper branch from f3b977a to 2a5a277 Compare October 8, 2026 06:22
@metamask-ci
metamask-ci Bot force-pushed the renovate/zjonsson-node-unzipper branch from 4b1b6c3 to d3405fc Compare October 23, 2026 06:18
@metamask-ci
metamask-ci Bot force-pushed the renovate/zjonsson-node-unzipper branch from a2ac97d to 75c3a4d Compare October 23, 2026 23:39
@metamask-ci
metamask-ci Bot force-pushed the renovate/zjonsson-node-unzipper branch from a8effc3 to 64f806c Compare October 25, 2026 06:14
@metamask-ci
metamask-ci Bot force-pushed the renovate/zjonsson-node-unzipper branch from 71a8aab to 35e638c Compare October 25, 2026 12:31
@metamask-ci
metamask-ci Bot force-pushed the renovate/zjonsson-node-unzipper branch from 13fd318 to bd21595 Compare November 4, 2026 06:13

This branch was previously deployed

2 inactive (outdated) deployments
default-branch — 16810991 Deployed Oct 7, 2026 by metamask-ci[bot] via Determine whether this PR is a release PR #5207
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