Skip to content

[Snyk] Security upgrade tar from 6.2.1 to 7.5.19#29

Open
winjer wants to merge 1 commit into
mainfrom
snyk-fix-ed47aa0cc74eabb21cb150d9d3da5fef
Open

[Snyk] Security upgrade tar from 6.2.1 to 7.5.19#29
winjer wants to merge 1 commit into
mainfrom
snyk-fix-ed47aa0cc74eabb21cb150d9d3da5fef

Conversation

@winjer

@winjer winjer commented Jul 10, 2026

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 4 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Infinite loop
SNYK-JS-TAR-17909068
  828  
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-TAR-17909152
  828  
medium severity Incorrect Type Conversion or Cast
SNYK-JS-TAR-17909104
  738  
medium severity Uncaught Exception
SNYK-JS-TAR-17909225
  738  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Uncaught Exception

@winjer

winjer commented Jul 10, 2026

Copy link
Copy Markdown
Author

Merge Risk: High

This is a major version upgrade that introduces significant breaking changes.

Key Breaking Changes in v7.0.0:

  • Node.js Support: Support for Node.js versions below 18 has been dropped.
  • File Permissions: The default behavior for setting file permissions during extraction has been reversed. The noChmod option is deprecated and replaced by a chmod option which now defaults to false. To restore the old behavior of applying file modes from the archive, you must explicitly set chmod: true in your options.
  • Module System: The package has been rewritten in TypeScript and now provides a hybrid ESM and CommonJS interface. This could affect how you import or require the module in your project.

Recommendation:

  • Ensure your environment is running Node.js 18 or newer.
  • Review any code that uses tar for extraction and add chmod: true to the options if you rely on file permissions being set from the archive.
  • Verify your import/require statements to ensure they are compatible with the new module structure.

Source: GitHub CHANGELOG.md

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

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.

2 participants