You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Published dist bundles source-map-js 1.2.1 (CVE-2026-93749) — could a release pick up 1.2.2? #184
Every magicast 0.5.x so far (0.5.0–0.5.5) inlines source-map-js 1.2.1 into dist/builders-*.js through the source-map → source-map-js alias. That version is affected by GHSA-68fv-2mgg-jv7q (CVE-2026-93749), which is fixed in 1.2.2. Because the copy is inlined, downstream overrides/resolutions can't patch it, and npm audit/Dependabot don't report it.
Real-world exposure looks limited, since the consumer is only built when an input source map is passed in. But code scanners will keep flagging the bundled copy. main's lockfile still resolves source-map-js to 1.2.1, and #144 or #161 would move it to 1.2.2. Would you consider merging one and cutting a patch release?
Activity