build(deps): Bump the npm_and_yarn group group with 2 updates

[dependabot[bot]]

Bumps the npm_and_yarn group group with 2 updates: es5-ext and ip.

Updates es5-ext from 0.10.62 to 0.10.64

Release notes

Sourced from es5-ext's releases.

0.10.64 (2024-02-27)

Bug Fixes

• Revert update to postinstall script meant to fix Powershell issue, as it's a regression for some Linux terminals (c2e2bb9)

---

Comparison since last release

0.10.63 (2024-02-23)

Bug Fixes

• Do not rely on problematic regex (3551cdd), addresses #201
• Support ES2015+ function definitions in function#toStringTokens() (a52e957), addresses #021
• Ensure postinstall script does not crash on Windows, fixes #181 (bf8ed79)

Maintenance Improvements

• Simplify the manifest message (7855319)

---

Comparison since last release

Changelog

Sourced from es5-ext's changelog.

0.10.64 (2024-02-27)

Bug Fixes

• Revert update to postinstall script meant to fix Powershell issue, as it's a regression for some Linux terminals (c2e2bb9)

0.10.63 (2024-02-23)

Bug Fixes

• Do not rely on problematic regex (3551cdd), addresses #201
• Support ES2015+ function definitions in function#toStringTokens() (a52e957), addresses #021
• Ensure postinstall script does not crash on Windows, fixes #181 (bf8ed79)

Maintenance Improvements

• Simplify the manifest message (7855319)

Commits

• f76b03d chore: Release v0.10.64
• 2881acd chore: Bump dependencies
• c2e2bb9 fix: Revert update meant to fix Powershell issue, as it's a regression
• 16f2b72 docs: Fix date in the changelog
• de4e03c chore: Release v0.10.63
• 3fd53b7 chore: Upgrade lint-staged to v13
• bf8ed79 chore: Ensure postinstall script does not crash on Windows
• 2cbbb07 chore: Bump dependencies
• 22d0416 chore: Bump LICENSE year
• a52e957 fix: Support ES2015+ function definitions in function#toStringTokens()
• Additional commits viewable in compare view

Updates ip from 2.0.0 to 2.0.1

Commits

• 3b0994a 2.0.1
• 32f468f lib: fixed CVE-2023-42282 and added unit test
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/storm-software/acidic/network/alerts).

[socket-security[bot]]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@storybook/jest@0.2.3	None	+6	1.67 MB	yannbf
npm/@storybook/react-vite@7.6.6	Transitive: environment, eval, filesystem, network, unsafe	+77	15.9 MB	shilman
npm/@storybook/react@7.6.6	Transitive: environment, filesystem, network, unsafe	+40	11.4 MB	shilman
npm/@storybook/test-runner@0.16.0	environment Transitive: eval, filesystem, network, shell, unsafe	+72	14.8 MB	shilman
npm/@storybook/testing-library@0.2.2	Transitive: environment	+8	4 MB	yannbf
npm/@storybook/theming@7.6.6	environment	+3	746 kB	shilman
npm/@swc-node/register@1.8.0	environment, filesystem Transitive: shell	+6	809 kB	broooooklyn
npm/@swc/cli@0.1.63	environment, filesystem Transitive: network, shell	+8	1.66 MB	kdy1
npm/@swc/core@1.3.101	environment, filesystem, shell	+3	628 kB	kdy1
npm/@swc/helpers@0.5.3	None	0	228 kB	kdy1
npm/@testing-library/react@14.0.0	environment	+11	9.24 MB	testing-library-bot
npm/@types/eslint@8.56.2	None	+2	243 kB	types
npm/@types/jest@29.5.11	None	0	78.7 kB	types
npm/@types/node@18.19.4	None	0	3.82 MB	types
npm/@types/node@20.9.0	None	0	3.92 MB	types
npm/@types/prettier@3.0.0	None	0	1.72 kB	types
npm/@types/react-dom@18.2.18	None	+3	464 kB	types
npm/@types/react@18.2.55	None	+2	431 kB	types
npm/@types/vscode@1.85.0	None	0	626 kB	types
npm/@typescript-eslint/eslint-plugin@6.13.2	None	+11	5.16 MB	jameshenry
npm/@typescript-eslint/parser@6.13.2	None	+4	1.36 MB	jameshenry
npm/@vitejs/plugin-react-swc@3.5.0	filesystem, unsafe Transitive: environment, shell	+4	661 kB	vitebot
npm/@vitejs/plugin-react@4.2.1	Transitive: environment, filesystem, unsafe	+35	8.06 MB	vitebot
npm/@vitest/coverage-v8@1.2.2	None	+7	737 kB	oreanno
npm/@vitest/ui@1.0.4	None	+1	914 kB	oreanno
npm/@vscode/vsce@2.21.1	environment, filesystem, shell	+1	4.26 MB	vscode-bot
npm/autoprefixer@10.4.13	environment Transitive: filesystem	+1	261 kB	ai
npm/bentocache@1.0.0-beta.7	None	+9	1.18 MB	julien-r44

🚮 Removed packages: npm/chalk@5.3.0, npm/chokidar@3.5.3, npm/class-variance-authority@0.7.0, npm/clsx@2.1.0, npm/commander@11.1.0, npm/espree@9.6.1, npm/glob@10.3.10, npm/postcss@8.4.35, npm/react-dom@18.2.0, npm/react-error-boundary@4.0.12, npm/react@18.2.0, npm/rimraf@5.0.5, npm/tailwind-merge@2.2.1, npm/tslib@2.6.2, npm/typescript@5.3.3

View full report↗︎

[socket-security[bot]]

🚨 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
Native code	npm/bufferutil@4.0.8	Location: Package overview	orphan: npm/bufferutil@4.0.8
Install scripts	npm/@swc/core@1.3.101	Install script: postinstall Source: node postinstall.js	package.json pnpm-lock.yaml

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

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.

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

• @SocketSecurity ignore npm/bufferutil@4.0.8
• @SocketSecurity ignore npm/@swc/core@1.3.101

[dependabot[bot]]

Superseded by #47.