Bump samsam and nise to latest versions

[fatso83]

Ensures consistency and less breakage when there are "circular" dependencies.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@sinonjs/[email protected]	None	+2	65.2 kB
npm/[email protected]	None	+3	1.6 MB	cjohansen, fatso83, mantoni, ...1 more

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

View full report↗︎

[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.

Alert	Package	Note	Source	CI
License Policy Violation	npm/[email protected]	License: MIT - undefined	docs/release-source/release/examples/package.json	⚠︎
License Policy Violation	npm/[email protected]	License: MIT - undefined	docs/release-source/release/examples/package.json	⚠︎
License Policy Violation	npm/[email protected]	License: MIT - undefined	docs/release-source/release/examples/package.json	⚠︎
License Policy Violation	npm/[email protected]	License: MIT - undefined	docs/release-source/release/examples/package.json	⚠︎
License Policy Violation	npm/[email protected]	License: MIT - undefined	docs/release-source/release/examples/package.json	⚠︎
License Policy Violation	npm/[email protected]	License: MIT - undefined	docs/release-source/release/examples/package.json	⚠︎
License Policy Violation	npm/[email protected]	License: MIT - Not allowed by license policy (npm metadata, package/package.json, package/LICENSE.md)	docs/release-source/release/examples/package.json	⚠︎
License Policy Violation	npm/[email protected]	License: MIT - undefined	package-lock.json package.json	⚠︎
License Policy Violation	npm/[email protected]	License: BSD-3-Clause - Not allowed by license policy (npm metadata, package/package.json, package/LICENSE)	package-lock.json package.json	⚠︎

View full report↗︎

Next steps

What is a license policy violation?

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Find a package that does not violate your license policy or adjust your policy to allow this package's license.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]