[DO NOT MERGE] Testing socket security

[zpao]

Resubmitting potential supply chain attack changes

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Test Plan

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/

Related issues/PRs

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@polka/[email protected]	None	0	4.48 kB	lukeed
npm/[email protected]	None	0	12 kB	stephenmathieson

🚮 Removed packages: npm/@polka/[email protected], npm/[email protected]

View full report↗︎

[slorber]

FYI @zpao looks like Socket does not really detect lockfile resolution problems and only report changes here

I'm also adding this "lockfile-lint" tool from Snyk founder in our lint pipeline:

npx lockfile-lint --path yarn.lock --type yarn --allowed-hosts yarn --validate-https --validate-package-names --validate-integrity --empty-hostname=false --allowed-package-name-aliases react-loadable string-width-cjs strip-ansi-cjs wrap-ansi-cjs