Conversation
|
@metamaskbot update-policies |
|
Policy update failed. You can review the logs or retry the policy update here |
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: browserify@16.5.2, mocha@9.2.2 |
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat 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 unmaintained packages?Package has not been updated in more than a year and may be unmaintained. Problems with the package may go unaddressed. Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance. Take a deeper look at the dependencyTake 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 packageIf 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 riskTo ignore an alert, reply with a comment starting with
|
|
@metamaskbot update-policies |
|
Policies updated |
Builds ready [80a1dcf]
Page Load Metrics (1696 ± 138 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## develop #20946 +/- ##
========================================
Coverage 68.25% 68.25%
========================================
Files 1006 1006
Lines 40184 40184
Branches 10742 10742
========================================
Hits 27424 27424
Misses 12760 12760 ☔ View full report in Codecov by Sentry. |
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
|
Brought these changes into: #20917 So going to close this PR. Thank you, @FrederikBolding |
Builds ready [48bd458]
Page Load Metrics (1446 ± 29 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
|
Reopened after chat with @jiexi . We agreed the browserify update is warranted to be done independently. |
"new author" ok, unrelated |
unmaintained ok; unrelated |
|
@legobeat Updated description and re-ran failed CI. Should be good to review! |
Builds ready [b17b181]
Page Load Metrics (1743 ± 78 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Description
Bumps Browserify to the latest version, this allows us to start using
readable-stream@v3features and also dedupes some dependencies.