Initial scaffolding for FE work

[davidckim]

Initial scaffolding for FE work

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@emotion/[email protected]	Transitive: environment, filesystem, unsafe	+60	11.2 MB	andarist, emmatown, emotion-release-bot, ...1 more
npm/@emotion/[email protected]	Transitive: environment, filesystem, unsafe	+56	10.3 MB	andarist, emmatown, emotion-release-bot, ...1 more
npm/@mui/[email protected]	environment	+26	11.5 MB	mnajdova
npm/@testing-library/[email protected]	None	+15	2.45 MB	brrianalexis, cmckinstry, dfcook, ...13 more
npm/@testing-library/[email protected]	environment Transitive: eval	+21	3.99 MB	testing-library-bot
npm/@testing-library/[email protected]	Transitive: environment, eval	+21	3.82 MB	testing-library-bot
npm/@types/[email protected]	Transitive: environment, eval	+13	440 kB	types
npm/@types/[email protected]	None	0	1.84 MB	types
npm/@types/[email protected]	None	0	0 B
npm/@types/[email protected]	None	+2	1.69 MB	types
npm/@types/[email protected]	Transitive: environment	+4	1.34 MB	types
npm/[email protected]	environment, filesystem, network Transitive: eval, unsafe	+64	2.16 MB	ulisesgascon
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+90	9.79 MB	simenb
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+279	20.2 MB	simenb
npm/[email protected]	environment	+3	4.63 MB	react-bot
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+1175	132 MB	iansu
npm/[email protected]	environment	+2	339 kB	react-bot
npm/[email protected]	Transitive: environment, filesystem, network, shell	+8	2.62 MB	darrachequesne
npm/[email protected]	filesystem, network Transitive: environment	+18	2.15 MB	darrachequesne
npm/[email protected]	environment Transitive: filesystem	+16	3.83 MB	probablyup
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+143	15.8 MB	anhpnnd, kul, tsjest
npm/[email protected]	None	0	145 kB	philipwalton

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 contains potential security risks and anomalies that could lead to data leaks, environment manipulation, or obfuscated communication. It should be further reviewed and analyzed for any potential malicious behavior. Confidence: 1.00 Severity: 0.60	resources/gaming-fe/package-lock.json resources/gaming-fe/package.json	🚫
AI-detected potential code anomaly	npm/@pmmmwh/[email protected]	Notes: The code contains multiple anomalies including hardcoded environment variable, unusual conditions, potential backdoor, dynamic function creation, and dynamic module injections, which indicate a high probability of malicious behavior or security risks. Confidence: 1.00 Severity: 0.60	resources/gaming-fe/package-lock.json resources/gaming-fe/package.json	🚫
Install scripts	npm/[email protected]	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"	resources/gaming-fe/package-lock.json resources/gaming-fe/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.

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time 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/@pmmmwh/[email protected]
• @SocketSecurity ignore npm/[email protected]