Dev into main

[hensha256]

No description provided.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@fastify/[email protected]	None	0	80.2 kB	gurgunday
npm/@nomicfoundation/[email protected]	None	0	13.2 MB	nomic-foundation-publisher
npm/@nomicfoundation/[email protected]	None	0	13.8 MB	nomic-foundation-publisher
npm/@nomicfoundation/[email protected]	None	0	18.9 MB	nomic-foundation-publisher
npm/@nomicfoundation/[email protected]	None	0	18.9 MB	nomic-foundation-publisher
npm/@nomicfoundation/[email protected]	None	0	21 MB	nomic-foundation-publisher
npm/@nomicfoundation/[email protected]	None	0	20.9 MB	nomic-foundation-publisher
npm/@nomicfoundation/[email protected]	None	0	15.3 MB	nomic-foundation-publisher
npm/@nomicfoundation/[email protected]	filesystem, shell	0	306 kB	nomic-foundation-publisher
npm/@nomicfoundation/[email protected]	None	0	649 kB	fvictorio
npm/@nomicfoundation/[email protected]	None	0	125 kB	fvictorio
npm/@nomicfoundation/[email protected]	None	+2	1.5 MB	fvictorio
npm/@nomicfoundation/[email protected]	network	0	545 kB	fvictorio
npm/@nomicfoundation/[email protected]	filesystem, shell	0	25.6 kB	schaable
npm/@openzeppelin/[email protected]	None	0	1.7 MB	frangio
npm/[email protected]	None	+1	12.8 kB	nexdrew
npm/[email protected]	None	+4	198 kB	sindresorhus
npm/[email protected]	None	0	6.14 kB	sindresorhus
npm/[email protected]	environment, filesystem, shell	0	151 kB	abetomo
npm/[email protected]	Transitive: environment, filesystem	+2	2.9 MB	alcuadrado, fvictorio, fzeoli, ...3 more
npm/[email protected]	None	0	343 kB	faleij
npm/[email protected]	None	+1	9.2 MB	r0qs
npm/[email protected]	environment, network, unsafe	0	1.17 MB	matteo.collina
npm/[email protected]	None	0	3.73 kB	sindresorhus

🚮 Removed packages: npm/@nomicfoundation/[email protected], npm/@nomicfoundation/[email protected], npm/@nomicfoundation/[email protected], npm/@nomicfoundation/[email protected], npm/@nomicfoundation/[email protected], npm/@nomicfoundation/[email protected], npm/@nomicfoundation/[email protected], npm/@nomicfoundation/[email protected], npm/@nomicfoundation/[email protected], npm/@nomicfoundation/[email protected], npm/@nomicfoundation/[email protected], npm/@openzeppelin/[email protected], npm/@types/[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], 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], 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], 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/[email protected]	Notes: The code appears to be a WebAssembly (WASM) module implementing HTTP parsing functionality. The code contains suspicious elements such as ability to handle HTTP headers, message bodies, and chunk extensions. While it may be legitimate parser code, the obfuscated nature and presence of low-level binary operations warrants careful review due to potential for misuse in HTTP request/response manipulation or header injection attacks. Confidence: 1.00 Severity: 0.60	yarn.lock	⚠︎
AI-detected potential code anomaly	npm/[email protected]	Notes: The code appears to be a WebAssembly (WASM) module implementing HTTP parsing functionality. The code contains suspicious elements such as ability to handle HTTP headers, message bodies, and chunk extensions. While it may be legitimate parser code, the obfuscated nature and presence of low-level binary operations warrants careful review due to potential for misuse in HTTP request/response manipulation or header injection attacks. Confidence: 1.00 Severity: 0.60	yarn.lock	⚠︎
Shell access	npm/@nomicfoundation/[email protected]	Module: child_process Location: Package overview	package.json yarn.lock	⚠︎
Filesystem access	npm/@nomicfoundation/[email protected]	Module: fs Location: Package overview	package.json yarn.lock	⚠︎
Filesystem access	npm/[email protected]	Module: fs/promises Location: Package overview	package.json yarn.lock	⚠︎
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	package.json yarn.lock	⚠︎
Filesystem access	npm/[email protected]	Module: fs/promises Location: Package overview	package.json yarn.lock	⚠︎
Filesystem access	npm/@nomicfoundation/[email protected]	Module: fs Location: Package overview	yarn.lock	⚠︎
Shell access	npm/@nomicfoundation/[email protected]	Module: child_process Location: Package overview	yarn.lock	⚠︎

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.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

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/[email protected]
• @SocketSecurity ignore npm/@nomicfoundation/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@nomicfoundation/[email protected]