Update

[Justman100]

No description provided.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@rollup/plugin-json@6.1.0	Transitive: environment, filesystem	+19	36.1 MB	shellscape
npm/eslint@8.57.0	environment, filesystem Transitive: eval, shell, unsafe	+96	10.7 MB	eslintbot
npm/husky@9.0.11	environment, filesystem, shell	0	3.61 kB	typicode
npm/lint-staged@15.2.2	Transitive: environment, filesystem, shell	+54	2.48 MB	okonet
npm/rimraf@5.0.5	environment, filesystem Transitive: shell	+33	3.27 MB	isaacs
npm/rollup-plugin-serve@2.0.3	filesystem, network Transitive: shell	+2	84.5 kB	thgh
npm/rollup@4.12.0	environment, filesystem	+15	35.8 MB	lukastaegert

🚮 Removed packages: npm/@rollup/plugin-json@6.0.0, npm/eslint@8.36.0, npm/husky@8.0.3, npm/lint-staged@13.2.0, npm/rimraf@4.4.1, npm/rollup-plugin-serve@2.0.2, npm/rollup@3.20.2

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
Dynamic require	npm/rollup@4.12.0	Location: Package overview	package.json

View full report↗︎

Next steps

What is dynamic require?

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable 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 ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/rollup@4.12.0

[Justman100]

@victornpb