Release 1.7.19

[TheLastCicada]

No description provided.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@babel/[email protected]	Transitive: environment, eval, filesystem, network, shell	+36	2.09 MB	existentialism, hzoo, jlhwung, ...1 more
npm/@babel/[email protected]	environment, filesystem, unsafe Transitive: shell	+37	11.2 MB	nicolo-ribaudo
npm/@babel/[email protected]	unsafe	+5	293 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	+1	18.3 kB	existentialism, hzoo, jlhwung, ...1 more
npm/@babel/[email protected]	Transitive: environment, filesystem, shell, unsafe	+128	13.9 MB	existentialism, hzoo, jlhwung, ...1 more
npm/@babel/[email protected]	Transitive: filesystem, unsafe	+15	1.06 MB	existentialism, hzoo, jlhwung, ...1 more
npm/@eslint/[email protected]	None	0	14.6 kB	eslintbot
npm/@yao-pkg/[email protected]	environment, filesystem, network, shell, unsafe Transitive: eval	+133	14.9 MB	roberts_lando
npm/[email protected]	network Transitive: environment, eval, filesystem	+44	2 MB	chaijs
npm/[email protected]	None	+5	625 kB	chaijs
npm/[email protected]	environment Transitive: filesystem, shell, unsafe	+73	9.97 MB	eslintbot
npm/[email protected]	environment, filesystem, network Transitive: eval, unsafe	+57	1.62 MB	ulisesgascon
npm/[email protected]	None	0	176 kB	sindresorhus
npm/[email protected]	environment, eval, filesystem	+57	4.23 MB	joshuakgoldberg, uzlopak, voxpelli
npm/[email protected]	filesystem Transitive: environment	+18	13.9 MB	sdepold
npm/[email protected]	Transitive: environment, eval	+12	7.96 MB	cjohansen, fatso83, mantoni, ...1 more
npm/[email protected]	Transitive: environment, filesystem, network, shell	+8	2.62 MB	darrachequesne
npm/[email protected]	filesystem, network Transitive: environment	+18	4.61 MB	darrachequesne
npm/[email protected]	Transitive: environment	+38	2.45 MB	dabh

🚮 Removed packages: npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@eslint/[email protected], npm/@yao-pkg/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[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.

Alert	Package	Note	Source	CI
AI-detected potential code anomaly	npm/@yao-pkg/[email protected]	Notes: The code involves dynamically executing JavaScript code using the vm.Script module and managing child processes to handle this execution. This approach is inherently risky as it allows for arbitrary code execution and has potential security implications if the input data is not properly sanitized. However, there are no explicit signs of malicious intent such as data theft or system damage. The main concerns are related to the potential misuse of dynamic code execution and process management, which could be exploited in a supply chain attack scenario. Confidence: 0.80 Severity: 0.65	package-lock.json package.json	🚫

View full report↗︎

Next steps

What is an AI-detected potential code anomaly?

AI has identified unusual behaviors that may pose a security risk.

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.

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 ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@yao-pkg/[email protected]

[TheLastCicada]

@SocketSecurity ignore npm/@yao-pkg/[email protected]