fun

Summary hard-pins an exact, deprecated version of , and the pin is still present in the latest release (). Because it's an exact pin (no range), downstream consumers — including the CLI — can't pick up the fixed transitively even after updating everything. Where (and ) : Why it matters is deprecated on npm — the maintainer's notice reads: "Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version." The current release is . Recent node-tar advisories in the 7.x line (2025–2026) include, among others: GHSA-r6q2-hw4h-h46w — race condition on macOS APFS (High, 8.8) GHSA-9ppj-qmqm-q256 — symlink path traversal (High, 8.2) GHSA-qffp-2rhf-9h96 — hardlink path traversal (High, 8.2) GHSA-34x7-hfp2-rc4v — arbitrary file create/overwrite (High, 8.2) GHSA-8qq5-rm4j-mr97 — file overwrite / symlink poisoning (High, 8.2) Because the pin is exact, this can't be resolved downstream: stays on even after (which correctly moves npm's own copy to ) and reinstalling the CLI. Suggested fix Loosen the pin so patched releases resolve automatically: (or at minimum , matching what in the same dependency tree already uses.) Environment 1.3.0 / 1.3.1 (latest) pulled in via the CLI 54.18.7 npm 11.18.0, Node 24.14.0, macOS

Problem The published runtime dependency tree still contains seven audit advisories through exact pins to and . This includes one critical, two high, three moderate, and one low advisory. Root cause Both dependencies are pinned below their patched releases, so normal lockfile resolution cannot move them forward. Change Update to . Update to . Regenerate . This is a minimal patch for the currently shipped tar-based implementation. It complements #142, which may replace tar entirely; the update remains necessary independently. Verification : 37 tests passed. : 7 advisories before, 0 after. Full : 45 advisories before, 39 after; the remaining findings are development dependencies.