WIP: Update Prettier and ESLint

[valentinpalkovic]

No description provided.

[socket-security]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
eslint-config-prettier	8.3.0...9.1.0	None	+2/-107	3.58 MB	lydell
remark-cli	9.0.0...12.0.0	None	+2/-125	499 kB	wooorm
prettier	2.3.1...3.1.0	None	+0/-0	8.44 MB	prettier-bot
eslint	7.28.0...8.55.0	None	+1/-106	3.56 MB	eslintbot
typescript	4.3.4...5.3.2	None	+0/-0	32 MB	typescript-bot

🚮 Removed packages: @types/[email protected], @typescript-eslint/[email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]

[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
New author	nopt	7.2.0	New Author: npm-cli-ops Previous Author: gar	[email protected] via package.json
New author	create-jest	29.7.0	New Author: simenb Previous Author: cpojer	[email protected], [email protected] via package.json
Shell access	update-browserslist-db	1.0.13	Module: child_process Location: check-npm-version.js +1 more instances...	[email protected], [email protected] via package.json
Uses eval	js-yaml	3.14.1	Eval Type: Function Location: dist/js-yaml.min.js +1 more instances...	[email protected], [email protected] via package.json
Uses eval	uvu	0.5.6	Eval Type: Function Location: bin.js +1 more instances...	[email protected], [email protected] via package.json

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

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 eval?

Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use eval, since this could potentially execute any code.

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