MetaMask / api-playground

https://metamask.github.io/api-playground/api-documentation
Apache License 2.0
6 stars 12 forks source link

Update lavamoat #61

Open BelfordZ opened 2 years ago

socket-security[bot] commented 1 year ago

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

Packages Version New capabilities Transitives Size Publisher
gatsby-plugin-mdx 2.14.1...2.15.0 None +16/-5 2.26 MB pieh

🚮 Removed packages: @lavamoat/allow-scripts@1.0.5

socket-security[bot] commented 1 year ago

🚨 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
Critical CVE minimist 1.2.5
Critical CVE @babel/traverse 7.13.13
Critical CVE url-parse 1.5.7
Mild CVE url-parse 1.5.7
CVE terser 4.8.0
CVE devcert 1.1.3
CVE decode-uri-component 0.2.0
CVE moment 2.29.1
CVE jpeg-js 0.4.3
CVE ua-parser-js 0.7.27
CVE json5 2.2.0
CVE qs 6.10.1
CVE axios 0.21.1
Install scripts @lavamoat/aa 3.1.5
New author @lavamoat/aa 3.1.5
Mild CVE browserslist 4.16.3
Mild CVE semver 5.7.1
Mild CVE semver 6.3.0
Mild CVE semver 7.0.0
Mild CVE semver 7.3.5
Mild CVE semver 7.3.7
Mild CVE word-wrap 1.2.3
Mild CVE follow-redirects 1.14.7
Mild CVE @sideway/formula 3.0.0
New author destroy 1.0.4
New author regexpu-core 4.7.1
New author @babel/helper-skip-transparent-expression-wrappers 7.12.1
New author nopt 6.0.0
No README @babel/compat-data 7.13.12
No README @babel/helper-compilation-targets 7.13.13
No README @babel/plugin-transform-react-jsx-development 7.12.17
No README @babel/plugin-transform-react-pure-annotations 7.12.1

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is a mild CVE?

Contains a low severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known low severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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.

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.

Why are READMEs important?

Package does not have a README. This may indicate a failed publish or a low quality package.

Add a README to to the package and publish a new version.

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 foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore terser@4.8.0
  • @SocketSecurity ignore devcert@1.1.3
  • @SocketSecurity ignore decode-uri-component@0.2.0
  • @SocketSecurity ignore moment@2.29.1
  • @SocketSecurity ignore jpeg-js@0.4.3
  • @SocketSecurity ignore ua-parser-js@0.7.27
  • @SocketSecurity ignore json5@2.2.0
  • @SocketSecurity ignore qs@6.10.1
  • @SocketSecurity ignore axios@0.21.1
  • @SocketSecurity ignore browserslist@4.16.3
  • @SocketSecurity ignore semver@5.7.1
  • @SocketSecurity ignore semver@6.3.0
  • @SocketSecurity ignore semver@7.0.0
  • @SocketSecurity ignore semver@7.3.5
  • @SocketSecurity ignore semver@7.3.7
  • @SocketSecurity ignore word-wrap@1.2.3
  • @SocketSecurity ignore follow-redirects@1.14.7
  • @SocketSecurity ignore @sideway/formula@3.0.0
  • @SocketSecurity ignore url-parse@1.5.7
  • @SocketSecurity ignore @babel/compat-data@7.13.12
  • @SocketSecurity ignore @babel/helper-compilation-targets@7.13.13
  • @SocketSecurity ignore @babel/plugin-transform-react-jsx-development@7.12.17
  • @SocketSecurity ignore @babel/plugin-transform-react-pure-annotations@7.12.1
  • @SocketSecurity ignore destroy@1.0.4
  • @SocketSecurity ignore regexpu-core@4.7.1
  • @SocketSecurity ignore @babel/helper-skip-transparent-expression-wrappers@7.12.1
  • @SocketSecurity ignore nopt@6.0.0
  • @SocketSecurity ignore @lavamoat/aa@3.1.5
  • @SocketSecurity ignore minimist@1.2.5
  • @SocketSecurity ignore @babel/traverse@7.13.13