Add more flexible query script

[Mrtenz]

This replaces the query script with a CLI.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	64.4 kB	matteo.collina
npm/[email protected]	None	0	82.5 kB	feross
npm/[email protected]	None	0	4.37 kB	sindresorhus
npm/[email protected]	None	0	11.1 kB	pvorb
npm/[email protected]	None	0	3.84 kB	sindresorhus
npm/[email protected]	None	0	4.62 kB	sindresorhus
npm/[email protected]	None	0	3.54 kB	sindresorhus
npm/[email protected]	None	0	4.58 kB	sindresorhus
npm/[email protected]	None	0	23.2 kB	sindresorhus
npm/[email protected]	None	0	2.82 kB	sindresorhus
npm/[email protected]	None	0	14.2 kB	timoxley

🚮 Removed packages: 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
New author	npm/[email protected]	New Author: sindresorhus Previous Author: tmpvar

View full report↗︎

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.

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]