chore: Bump tar from 7.5.12 to 7.5.21 - #4087

Notes: This module acts as a standard tar extraction wrapper using synchronous and asynchronous code paths. There is no evident malicious activity within this fragment. Security risk hinges on the behavior of the Unpack/UnpackSync implementation and how tar entries are written to disk (e.g., path traversal). No hardcoded secrets or network calls are present here. Recommend ensuring tar extraction handles path traversal and destination path sanitization in Unpack, and consider validating opt.file presence and type before streaming.

Confidence: 0.66

Severity: 0.56

From: ? → npm/@lavamoat/allow-scripts@4.0.0 → npm/rollup@2.80.0 → npm/vite@6.4.3 → npm/crypto-browserify@3.12.1 → npm/@jest/expect@29.5.0 → npm/jest@29.5.0 → npm/webpack-dev-server@5.2.2 → npm/fork-ts-checker-webpack-plugin@9.0.2 → npm/tsx@4.20.3 → npm/ts-jest@29.1.1 → npm/playwright@1.57.0 → npm/tar@7.5.21

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tar@7.5.21. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.