Skip to content

version bump

4ec369d
Select commit
Loading
Failed to load commit list.
Merged

Eric/cus 48 try to detect truncated results in full scan results and #42

version bump
4ec369d
Select commit
Loading
Failed to load commit list.
Socket Security Staging / Socket Security Staging: Pull Request Alerts succeeded Jan 24, 2025 in 8s

Pull Request #42 Alerts: Complete with warnings

Report Status Message
PR #42 Alerts ⚠️ Found 4 project alerts

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
Unpopular package pypi/[email protected] ⚠︎
License Policy Violation pypi/[email protected] ⚠︎
License Policy Violation pypi/[email protected] ⚠︎

View full report↗︎

Next steps

What are unpopular packages?

This package is not very popular.

Unpopular packages may have less maintenance and contain other problems.

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