BETA VERSION 0.68.1

[Mittelblut9]

View release notes

[pull-request-checklist-buddy]

Beta Branch checks

• Release npm version updated?
• Code works as expected?
• All Code checks are successfully? (Alerts from Socket Security should be checked and ignored for this checkpoint)
• Debug Code removed?
• Code Review approved?

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Modified license	domhandler	5.0.3	License: BSD-2-Clause Similarity: 0.96 +1 more instances...	@discord-player/[email protected], [email protected] via package.json
Modified license	esprima	4.0.1	License: BSD-2-Clause Similarity: 0.99 +2 more instances...	[email protected] via package.json
Modified license	source-map	0.6.1	License: BSD-3-Clause Similarity: 0.98 +1 more instances...	[email protected] via package.json
Modified license	detect-libc	2.0.2	License: Apache-2.0 Similarity: 0.99 +1 more instances...	@discordjs/[email protected], @discordjs/[email protected], @sentry/[email protected], [email protected] via package.json

Next steps

What is a modified license?

(Experimental) Package contains a modified version of an SPDX license. Please read carefully before using this code.

Packages should avoid making modifications to standard licenses.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore [email protected]
• @SocketSecurity ignore [email protected]
• @SocketSecurity ignore [email protected]
• @SocketSecurity ignore [email protected]