Skip to content
This repository was archived by the owner on Jan 22, 2025. It is now read-only.

chore: bump tinybench from 3.0.6 to 3.0.7 #3678

Merged
merged 1 commit into from
Dec 5, 2024

chore: bump tinybench from 3.0.6 to 3.0.7

558e845
Select commit
Loading
Failed to load commit list.
Merged

chore: bump tinybench from 3.0.6 to 3.0.7 #3678

chore: bump tinybench from 3.0.6 to 3.0.7
558e845
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts completed Dec 5, 2024 in 40s

Pull Request #3678 Alerts: Complete with warnings WARNING: Free tier size exceeded

Report Status Message
PR #3678 Alerts ⚠️ Found 1 project alert

Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.

Details

🚨 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 NoteSourceCI
Possible typosquat attack npm/[email protected] ⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

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