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

chore(deps-dev): bump @nestjs/core from 8.4.2 to 9.0.5 #13

Merged
merged 2 commits into from
Sep 5, 2024

Merge branch 'main' into dependabot/npm_and_yarn/nestjs/core-9.0.5

05e4d17
Select commit
Loading
Failed to load commit list.
Merged

chore(deps-dev): bump @nestjs/core from 8.4.2 to 9.0.5 #13

Merge branch 'main' into dependabot/npm_and_yarn/nestjs/core-9.0.5
05e4d17
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts completed Sep 5, 2024 in 16s

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

Report Status Message
PR #13 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
Critical CVE npm/[email protected] ⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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