Dependencies: Regen lockfiles

[ndelangen]

No description provided.

[socket-security]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
@storybook/ember	7.1.0-alpha.25...7.1.0	None	+0/-24	20.7 kB	shilman
@storybook/server-webpack5	7.1.0-alpha.25...7.1.0	None	+0/-40	43.8 kB	shilman

🚮 Removed packages: @angular/common@16.1.4, @angular/core@16.1.4, @storybook/addon-a11y@7.1.0-alpha.25, @storybook/addon-actions@7.1.0-alpha.25, @storybook/addon-backgrounds@7.1.0-alpha.25, @storybook/addon-controls@7.1.0-alpha.25, @storybook/addon-docs@7.1.0-alpha.25, @storybook/addon-essentials@7.1.0-alpha.25, @storybook/addon-highlight@7.1.0-alpha.25, @storybook/addon-links@7.1.0-alpha.25, @storybook/addon-storysource@7.1.0-alpha.25, @storybook/addon-viewport@7.1.0-alpha.25, @storybook/addons@7.1.0-alpha.25, @storybook/blocks@7.1.0-alpha.25, @storybook/cli@7.1.0-alpha.25, @storybook/components@7.1.0-alpha.25, @storybook/node-logger@7.1.0-alpha.25, @storybook/preview-web@7.1.0-alpha.25, @storybook/react@7.1.0-alpha.25, @storybook/react-webpack5@7.1.0-alpha.25, @storybook/server@7.1.0-alpha.25, @storybook/source-loader@7.1.0-alpha.25, @storybook/theming@7.1.0-alpha.25, @swc/core@1.3.68, @testing-library/jest-dom@5.16.5, rollup@3.26.2, storybook@7.1.0-alpha.25, svelte-check@3.4.5, vue-tsc@1.8.4, webpack@5.88.1

[socket-security]

🚨 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
New author	ssri	8.0.1	New Author: nlf Previous Author: isaacs	nextra-theme-docs@1.2.6 via test-storybooks/external-docs/package.json

Next steps

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.

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 ssri@8.0.1