URLs: https://github.com/Microsoft/TypeScript/blob/master/src/compiler/diagnosticMessages.json, https://github.com/jestjs/jest/issues/3845, https://github.com/kulshekhar/ts-jest/issues/4198, https://www.typescriptlang.org/tsconfig/#moduleResolution, ES2020.Date, ES2017.Date, https://kulshekhar.github.io/ts-jest/docs/getting-started/options/diagnostics, https://kulshekhar.github.io/ts-jest/docs/getting-started/presets#advanced, https://github.com/jestjs/jest/issues/9778, https://www.typescriptlang.org/tsconfig/#isolatedModules, https://blogs.msdn.microsoft.com/typescript/2018/01/31/announcing-typescript-2-7/#easier-ecmascript-module-interoperability, https://github.com/microsoft/TypeScript/wiki/Node-Target-Mapping

Location: Package overview

From: package-lock.json → npm/ts-jest@29.4.11

ℹ Read more on: This package | This alert | What are URL strings?

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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/ts-jest@29.4.11. 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.