fix: resolve image-size to image-size-next (CVE-2025-71329/71330)

[lcf2212dev]

Summary

metro@^0.87.0 (pulled into this monorepo) depends on image-size@^1.0.2, which currently resolves to an archived / unmaintained package still affected by:

• CVE-2025-71329 — DoS infinite loop (JXL/HEIF/JP2 zero-size boxes)
• CVE-2025-71330 — DoS infinite loop (ICNS zero entry length)

This PR adds a Yarn resolutions entry so nested image-size installs resolve to the community MIT drop-in image-size-next@2.1.0 (same public API as image-size@2.x, drop-in for Metro’s usage), and updates yarn.lock accordingly.

• npm: https://www.npmjs.com/package/image-size-next
• GitHub: https://github.com/lcf2212dev/image-size-next
• Announcement: https://x.com/lcf2212dev/status/2086886635791081634

Not affiliated with the original image-size maintainer.

Fixes / relates to #57888

Changelog

[GENERAL] [SECURITY] - Force resolution of vulnerable image-size to maintained image-size-next@2.1.0 (CVE-2025-71329 / CVE-2025-71330)

Test Plan

• Confirmed with Yarn classic 1.22.x that
  "resolutions": { "image-size": "npm:image-size-next@2.1.0" }
  installs image-size-next@2.1.0 into the image-size slot used by Metro.
• yarn.lock updated to the published tarball + integrity for image-size-next@2.1.0.
• Recommend CI: full install + existing Metro/asset pipeline tests.

Notes for reviewers

• Longer-term fix may live in facebook/metro (change the direct dependency). This monorepo resolution unblocks RN consumers immediately.
• npm audit fix cannot rename packages; an override/resolution is required.

[meta-cla]

Hi @lcf2212dev!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[github-actions]

Caution

Missing Changelog

Please add a Changelog to your PR description. See Changelog format

[lcf2212dev]

Closing in favor of a new PR with a properly signed commit (no force-push on this branch).