[Snyk] Security upgrade archiver from 5.3.1 to 8.0.0

[cc-prodsec]

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

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-15309438	756
	Inefficient Algorithmic Complexity SNYK-JS-MINIMATCH-15353389	756

Breaking Change Risk

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:

🦉 Regular Expression Denial of Service (ReDoS)

[cc-prodsec]

This major version upgrade from 5.3.1 to 8.0.0 includes significant breaking changes, most notably a change in API behavior and multiple drops of older Node.js versions.

Key Breaking Changes:

• v8.0.0 (Beta):
  • The behavior of the archiver.pointer() method has changed. It now returns the final pointer position instead of the total size of the archive. Code that relies on this method to get the total archive size will need to be updated.
  • Support for Node.js v14 has been dropped.
• v7.0.0:
  • Support for Node.js v12 has been dropped.
• v6.0.0:
  • Support for Node.js v10 has been dropped.

Recommendation:

Given the API behavior change and the multiple Node.js version requirements, this upgrade carries a high risk.

1. Verify Environment: Ensure your production environment is running Node.js v16 or newer.
2. Audit Code: Carefully review any usage of archiver.pointer() to ensure it's compatible with the new behavior. This change could lead to subtle bugs if not addressed.

Source: GitHub Releases

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

[cc-prodsec]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.