Don't merge, just testing something out

[kasperpeulen]

No description provided.

[github-actions]

	Fails
🚫	PR is not labeled with one of: ["cleanup","BREAKING CHANGE","feature request","bug","documentation","maintenance","build","dependencies"]
🚫	PR title must be in the format of "Area: Summary", With both Area and Summary starting with a capital letter Good examples: - "Docs: Describe Canvas Doc Block" - "Svelte: Support Svelte v4" Bad examples: - "add new api docs" - "fix: Svelte 4 support" - "Vue: improve docs"

Generated by 🚫 dangerJS against 2b9981a

[socket-security]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
@vitest/spy	0.34.7	None	+2	42.5 kB	oreanno
@types/jest	29.5.5	None	+0	79.9 kB	types
@vitest/expect	0.34.7	None	+22	2.23 MB	oreanno
chai	4.3.10	environment	+12	1.01 MB	keithamus

[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	pathval	1.1.1	New Author: chai Previous Author: chaijs	@storybook/addon-storyshots@0.0.0-use.local, @storybook/angular@0.0.0-use.local, @storybook/builder-manager@0.0.0-use.local, @storybook/cli@0.0.0-use.local, @storybook/core-server@0.0.0-use.local, @storybook/html-vite@0.0.0-use.local, @storybook/manager@0.0.0-use.local, @storybook/preset-server-webpack@0.0.0-use.local, @storybook/server-webpack5@0.0.0-use.local, @storybook/vue3-vite@0.0.0-use.local, @storybook/web-components-vite@0.0.0-use.local, @vitest/expect@0.34.7, chai@4.3.10 via code/package.json @vitest/expect@0.34.7, chai@4.3.10 via code/lib/test/package.json
New author	check-error	1.0.3	New Author: keithamus Previous Author: chaijs	@storybook/addon-storyshots@0.0.0-use.local, @storybook/angular@0.0.0-use.local, @storybook/builder-manager@0.0.0-use.local, @storybook/cli@0.0.0-use.local, @storybook/core-server@0.0.0-use.local, @storybook/html-vite@0.0.0-use.local, @storybook/manager@0.0.0-use.local, @storybook/preset-server-webpack@0.0.0-use.local, @storybook/server-webpack5@0.0.0-use.local, @storybook/vue3-vite@0.0.0-use.local, @storybook/web-components-vite@0.0.0-use.local, @vitest/expect@0.34.7, chai@4.3.10 via code/package.json @vitest/expect@0.34.7, chai@4.3.10 via code/lib/test/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 pathval@1.1.1
• @SocketSecurity ignore check-error@1.0.3