You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Low Risk
Patch-level dependency and types bump only, with lockfile refresh; no logic changes in foundryup.
Overview
Updates @metamask/foundryup dependency maintenance: unzipper is bumped from ^0.12.3 to ^0.12.5, and @types/unzipper from ^0.10.10 to ^0.10.11, with yarn.lock pinned to [email protected] (including its [email protected] dependency). The unreleased CHANGELOG entry documents the change.
No application code changes; unzipper remains the library used in extract.ts for zip archive handling alongside tar.
Reviewed by Cursor Bugbot for commit bd51b07. Bugbot is set up for automated code reviews on this repo. Configure here.
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
Action
Severity
Alert (click "▶" to expand/collapse)
Warn
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.).
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
[email protected].
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/[email protected]. 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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.12.3→^0.12.5^0.10.10→^0.10.11Release Notes
ZJONSSON/node-unzipper (unzipper)
v0.12.5Compare Source
v0.12.4Compare Source
Configuration
📅 Schedule: (UTC)
🚦 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 these updates again.
This PR has been generated by Mend Renovate CLI.
Note
Low Risk
Patch-level dependency and types bump only, with lockfile refresh; no logic changes in foundryup.
Overview
Updates
@metamask/foundryupdependency maintenance:unzipperis bumped from^0.12.3to^0.12.5, and@types/unzipperfrom^0.10.10to^0.10.11, withyarn.lockpinned to[email protected](including its[email protected]dependency). The unreleased CHANGELOG entry documents the change.No application code changes;
unzipperremains the library used inextract.tsfor zip archive handling alongsidetar.Reviewed by Cursor Bugbot for commit bd51b07. Bugbot is set up for automated code reviews on this repo. Configure here.