Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps-dev): bump @yao-pkg/pkg from 5.14.2 to 5.15.0 #1180

Closed
wants to merge 1 commit into from

build(deps-dev): bump @yao-pkg/pkg from 5.14.2 to 5.15.0

aecfaac
Select commit
Loading
Failed to load commit list.
Closed

build(deps-dev): bump @yao-pkg/pkg from 5.14.2 to 5.15.0 #1180

build(deps-dev): bump @yao-pkg/pkg from 5.14.2 to 5.15.0
aecfaac
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts failed Sep 24, 2024 in 14s

Pull Request #1180 Alerts: Complete with warnings

Report Status Message
PR #1180 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
AI-detected potential code anomaly npm/@yao-pkg/pkg@5.15.0
  • Notes: The code involves dynamically executing JavaScript code using the vm.Script module and managing child processes to handle this execution. This approach is inherently risky as it allows for arbitrary code execution and has potential security implications if the input data is not properly sanitized. However, there are no explicit signs of malicious intent such as data theft or system damage. The main concerns are related to the potential misuse of dynamic code execution and process management, which could be exploited in a supply chain attack scenario.
  • Confidence: 0.80
  • Severity: 0.65
 🚫

View full report↗︎

Next steps

What is an AI-detected potential code anomaly?

AI has identified unusual behaviors that may pose a security risk.

An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

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/@yao-pkg/pkg@5.15.0
View more details on Socket Security