deps: use forked license-checker with fixed dependencies

[legobeat]

Resolves several deprecated dependencies. Using forks because upstreams are unmaintained as of 2018~2019:

https://github.com/davglass/license-checker -> https://github.com/MetaMask/license-checker

https://github.com/jslicense/spdx-compare.js -> https://github.com/MetaMask/spdx-compare.js

This repository is used for metamask-mobile as of MetaMask/metamask-mobile#6306

---

Blocked by

• v26.0.1 license-checker#10
  • deps: spdx-satisfies@^5.0.1 -> @metamask/spdx-satisfies@^6.0.0 license-checker#9
    • Release @metamask/spdx-satisfies v6.0.0 spdx-satisfies.js#3

[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
New author	npm/[email protected]	New Author: gar Previous Author: isaacs	package-lock.json package.json
Unpublished package	npm/@metamask/[email protected]	Version: Invalid Date	package-lock.json package.json

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.

What are unpublished packages?

Package version was not found on the registry. It may exist on a different registry and need to be configured to pull from that registry.

Packages can be removed from the registry by manually un-publishing, a security issue removal, or may simply never have been published to the registry. Reliance on these packages will cause problem when they are not found.

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/@metamask/[email protected]

[legobeat]

@SocketSecurity ignore [email protected]

[legobeat]

@SocketSecurity ignore [email protected]

[legobeat]

@SocketSecurity ignore [email protected]

[legobeat]

@sethkfman Did you have a chance to take a look here yet? :)

MetaMask/metamask-mobile#6306 (comment)

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/[email protected]	Transitive: environment, filesystem	+54	1.08 MB

🚮 Removed packages: npm/[email protected]

View full report↗︎

[legobeat]

@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/@metamask/[email protected]

nopt: new author ok
@metamask/license-checker: is actually not unpublished; just recent

[Gudahtt]

LGTM!