Repository navigation
Security: vulnerable dependency image-size (CVE-2025-71329/71330) — maintained drop-in available #97107
lcf2212dev
started this conversation in
Ideas
Replies: 1 comment
|
This seems to be a bot with a new account literally spamming hundreds of repositories to promote a new supposed fork of the image-size library which he himself made. It appears that the proposed image-size-next library was just published too. Red flags everywhere on this, be warned. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Context
This package depends on npm
image-size. Upstream is archived and the latest release (2.0.2) remains affected by:npm audit fixwill not switch package names automatically.Maintained drop-in
Community MIT fork with the same public API as
image-size@2.0.2:image-size-next@2.1.0)Not affiliated with the original
image-sizemaintainer — honest community fork only.Migration options
A — Direct dependency
fromFile:image-size/fromFile→image-size-next/fromFileB — Force transitive resolution (npm 8.3+)
{ "overrides": { "image-size": "npm:image-size-next@2.1.0" } }Ask
Happy to open a PR if that helps. Flagging this so maintainers of
@nil1511/nextcan patch on their schedule.Thanks for maintaining open source.
All reactions