Closed georgewrmarshall closed 7 months ago
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@babel/core@7.23.5, npm/@babel/generator@7.23.5, npm/@babel/helper-compilation-targets@7.22.15, npm/@babel/helper-create-class-features-plugin@7.23.5, npm/@babel/parser@7.23.5, npm/@babel/preset-env@7.23.5, npm/@babel/runtime@7.23.5, npm/@babel/template@7.22.15, npm/@babel/traverse@7.23.5, npm/@babel/types@7.23.5, npm/@jridgewell/gen-mapping@0.3.2, npm/@jridgewell/trace-mapping@0.3.20, npm/@lavamoat/allow-scripts@1.0.6, npm/@metamask/eslint-config-jest@9.0.0, npm/@metamask/eslint-config-nodejs@9.0.0, npm/@metamask/eslint-config-typescript@9.0.1, npm/@metamask/eslint-config@9.0.0, npm/@storybook/addon-a11y@7.6.10, npm/@storybook/addon-actions@7.6.10, npm/@storybook/addon-essentials@7.6.10, npm/@storybook/addon-links@7.6.10, npm/@storybook/addon-mdx-gfm@7.6.10, npm/@storybook/react-webpack5@7.6.10, npm/@storybook/react@7.6.10, npm/@types/babel__traverse@7.20.4, npm/@types/istanbul-lib-coverage@2.0.4, npm/@types/jest@26.0.24, npm/@types/node@18.19.3, npm/@types/qs@6.9.10, npm/@typescript-eslint/eslint-plugin@4.33.0, npm/@typescript-eslint/experimental-utils@4.33.0, npm/@typescript-eslint/parser@4.33.0, npm/abab@2.0.6, npm/anymatch@3.1.2, npm/assert-plus@1.0.0, npm/babel-loader@8.2.5, npm/browserslist@4.22.2, npm/core-js-compat@3.34.0, npm/es-abstract@1.20.1, npm/eslint-config-prettier@8.5.0, npm/eslint-plugin-jest@24.7.0, npm/eslint-plugin-jsdoc@36.1.1, npm/eslint-plugin-prettier@3.4.1, npm/eslint@7.32.0, npm/espree@7.3.1, npm/extend-shallow@3.0.2, npm/extsprintf@1.3.0, npm/fast-glob@3.2.11, npm/get-value@2.0.6, npm/ignore@5.2.0, npm/is-descriptor@1.0.2, npm/is-extendable@0.1.1, npm/is-typedarray@1.0.0, npm/istanbul-lib-coverage@3.2.0, npm/jest-diff@26.6.2, npm/jest@26.6.3, npm/minimist@1.2.6, npm/object-inspect@1.12.2, npm/postcss-modules-local-by-default@4.0.3, npm/postcss-selector-parser@6.0.10, npm/postcss@8.4.32, npm/prettier-plugin-packagejson@2.2.18, npm/pretty-format@26.6.2, npm/psl@1.9.0, npm/punycode@2.1.1, npm/regex-not@1.0.2, npm/sass@1.54.3, npm/set-value@2.0.1, npm/split-string@3.1.0, npm/storybook@7.6.10, npm/terser-webpack-plugin@5.3.9, npm/terser@5.26.0, npm/to-regex@3.0.2, npm/ts-jest@26.5.6, npm/tsconfig-paths@3.14.1, npm/tweetnacl@0.14.5, npm/typescript@4.7.4, npm/whatwg-url@8.7.0, npm/which-typed-array@1.1.13
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎
To accept the risk, merge this PR and you will not be notified again.
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.
This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.
This module accesses the network.
Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.
Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.
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.
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.
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.
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/foo@1.0.0
or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/istanbul-lib-report@3.0.1
@SocketSecurity ignore npm/anymatch@3.1.3
@SocketSecurity ignore npm/fb-watchman@2.0.2
@SocketSecurity ignore npm/supports-hyperlinks@2.3.0
@SocketSecurity ignore npm/react-is@18.2.0
@SocketSecurity ignore npm/fast-diff@1.3.0
@SocketSecurity ignore npm/tree-kill@1.2.2
@SocketSecurity ignore npm/resolve-dir@1.0.1
@SocketSecurity ignore npm/expand-tilde@2.0.2
@SocketSecurity ignore npm/global-prefix@1.0.2
@SocketSecurity ignore npm/npm-normalize-package-bin@3.0.1
@SocketSecurity ignore npm/write-file-atomic@5.0.1
@SocketSecurity ignore npm/which@3.0.1
@SocketSecurity ignore npm/exponential-backoff@3.1.1
@SocketSecurity ignore npm/socks@2.7.1
@SocketSecurity ignore npm/agentkeepalive@4.5.0
@SocketSecurity ignore npm/@npmcli/fs@2.1.2
@SocketSecurity ignore npm/@npmcli/move-file@2.0.1
@SocketSecurity ignore npm/are-we-there-yet@3.0.1
@SocketSecurity ignore npm/make-fetch-happen@10.2.1
@SocketSecurity ignore npm/minipass-fetch@2.1.2
@SocketSecurity ignore npm/nopt@6.0.0
@SocketSecurity ignore npm/npmlog@6.0.2
@SocketSecurity ignore npm/socks-proxy-agent@7.0.0
@SocketSecurity ignore npm/source-map@0.8.0-beta.0
@SocketSecurity ignore npm/@npmcli/agent@2.2.0
@SocketSecurity ignore npm/handlebars@4.7.8
@SocketSecurity ignore npm/@npmcli/node-gyp@3.0.0
@SocketSecurity ignore npm/read-cmd-shim@4.0.0
@SocketSecurity ignore npm/@lavamoat/preinstall-always-fail@1.0.3
@SocketSecurity ignore npm/unique-slug@3.0.0
@SocketSecurity ignore npm/socks-proxy-agent@8.0.2
@SocketSecurity
Builds ready [42e9e0c]
Storybook: Storybook
Builds ready [899f18a]
Storybook: Storybook
Builds ready [7cca0b9]
Storybook: Storybook
Builds ready [55c3be3]
Storybook: Storybook
Socket dev security issues should be mitigated by lavamoat as they are all supply chain issues
Builds ready [fd4e72b]
Storybook: Storybook
Builds ready [c9e9380]
Storybook: Storybook
Builds ready [aaba235]
Storybook: Storybook
Description
This PR aims to update the design token package, which was originally generated from the metamask-module-template. Over time, the package has become outdated and incompatible with mobile and portfolio due to dependency issues, particularly with node versions. This PR addresses these issues by updating the dependencies and aligning the package with the most recent module template using the template sync package.
The upgrade to yarn version 3 also necessitated changes to the GitHub workflow files, which were updated to align with the module template. This alignment should enhance the automation of our releases. Due to the upgraded node and yarn versions, this PR includes numerous other dependency updates, file changes, lint fixes, and the inclusion of config files.
Fixes: #597
Manual Testing Steps
Because mobile and portfolio are using yarn v1 and the design tokens is using v3. It's quite hard to test using yarn link. But if you pull this branch and try to use yarn link on a project that use yarn 3 it will work like the module template.
yarn && yarn build
yarn link ../path/to/design-tokens
brandColor
in to theindex.ts
fileOther smoke tests
yarn storybook
Screencasts/Screenshots
Screencast below shows yarn link version of the design-tokens to the module-template as a test to ensure that the
brandColor
object in thev1.13
release is importing and working as intendedhttps://github.com/MetaMask/design-tokens/assets/8112138/5e5f52c4-3be1-462a-8c02-bbe5f4b5912d