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.

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

Bump aws-cdk-lib from 2.116.1 to 2.117.0 #133

Merged
merged 1 commit into from
Dec 28, 2023

Bump aws-cdk-lib from 2.116.1 to 2.117.0

695577d
Select commit
Loading
Failed to load commit list.
Merged

Bump aws-cdk-lib from 2.116.1 to 2.117.0 #133

Bump aws-cdk-lib from 2.116.1 to 2.117.0
695577d
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts failed Dec 28, 2023 in 5m 17s

Pull Request #133 Alerts: Complete with warnings

Report Status Message
PR #133 Alerts ⚠️ Found 50 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.

Issue Package Version Note Source
Minified code aws-cdk-lib 2.117.0
Mixed license aws-cdk-lib 2.117.0

Next steps

What's wrong with minified code?

This package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code.

In many cases minified code is harmless, however minified code can be used to hide a supply chain attack. Consider not shipping minified code on npm.

What is a mixed license?

(Experimental) Package contains multiple licenses.

A new version of the package should be published that includes a single license. Consumers may seek clarification from the package author. Ensure that the license details are consistent across the LICENSE file, package.json license field and license details mentioned in the README.

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 aws-cdk-lib@2.117.0