fix: resolve tar vulnerabilities (CVE-2026-23745, CVE-2026-23950, CVE-2026-24842)

[kherembourg]

Summary

• Update tar yarn resolution in root package.json from >=7.5.4 to >=7.5.7
• Add npm overrides in test-projects/expo-purchasely-test/package.json to force tar to >=7.5.7
• Regenerated both yarn.lock and package-lock.json (tar now resolves to 7.5.9)

Security

Fixes 3 Dependabot alerts:

• #525 — node-tar <= 7.5.2: Arbitrary File Overwrite and Symlink Poisoning (CVE-2026-23745, High)
• #526 — node-tar <= 7.5.3: Race Condition via Unicode Ligature Collisions on macOS APFS (CVE-2026-23950, High)
• #530 — node-tar < 7.5.7: Arbitrary File Creation/Overwrite via Hardlink Path Traversal (CVE-2026-24842, High)

Test plan

• yarn install succeeds in root workspace
• npm install succeeds in expo test project
• Verified tar resolves to 7.5.9 in both lock files

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @kherembourg, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the project's security posture by upgrading the node-tar dependency to mitigate several high-severity vulnerabilities. The changes involve updating dependency declarations and lock files across the repository to ensure that a secure version of tar is used consistently, thereby protecting against potential arbitrary file operations and race conditions.

Highlights

• Dependency Update: Updated the tar dependency resolution in the root package.json from >=7.5.4 to >=7.5.7.
• Dependency Overrides: Introduced npm overrides in test-projects/expo-purchasely-test/package.json to ensure tar resolves to >=7.5.7.
• Lock File Regeneration: Regenerated both yarn.lock and package-lock.json, resulting in tar resolving to version 7.5.9.
• Security Fixes: Addressed three high-severity node-tar vulnerabilities (CVE-2026-23745, CVE-2026-23950, CVE-2026-24842) related to arbitrary file overwrite, symlink poisoning, race conditions, and hardlink path traversal.

Changelog

• package.json
  • Updated tar dependency to >=7.5.7.
• test-projects/expo-purchasely-test/package-lock.json
  • Updated @purchasely/react-native-purchasely-android-player from 5.6.1 to 5.6.2.
  • Updated @purchasely/react-native-purchasely-google from 5.6.1 to 5.6.2.
  • Updated react-native-purchasely from 5.6.1 to 5.6.2.
  • Updated tar from 7.5.2 to 7.5.9.
• test-projects/expo-purchasely-test/package.json
  • Added overrides for tar to enforce version >=7.5.7.
• yarn.lock
  • Updated tar resolution from >=7.5.4 to >=7.5.7 and its version from 7.5.7 to 7.5.9.

Activity

• The initial changes were generated using Claude Code.
• The author verified that yarn install successfully completes in the root workspace.
• The author verified that npm install successfully completes in the expo test project.
• The author verified that the tar package resolves to version 7.5.9 in both yarn.lock and package-lock.json.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request effectively addresses the tar vulnerabilities by updating the version constraints in both yarn resolutions and npm overrides. The lock files have been regenerated accordingly, and tar is now resolved to a secure version. I've noted one minor issue regarding an undocumented dependency upgrade in the test project's lock file, which seems to be a side-effect of the update process. Please see the specific comment for details.