-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(deps): update dependency @types/node to v18.19.68 #495
base: main
Are you sure you want to change the base?
Conversation
3b4c554
to
f21de7f
Compare
f21de7f
to
13e8762
Compare
13e8762
to
2b897fc
Compare
2b897fc
to
7c6cb0b
Compare
7c6cb0b
to
e88660f
Compare
e88660f
to
2467c22
Compare
2467c22
to
dc094d3
Compare
dc094d3
to
bc9c987
Compare
bc9c987
to
27198d0
Compare
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat 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. 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 dependencyTake 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 packageIf 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 riskTo ignore an alert, reply with a comment starting with
|
27198d0
to
db4ca94
Compare
16ba554
to
a0df2ff
Compare
a0df2ff
to
d64738a
Compare
d64738a
to
80a2f1c
Compare
80a2f1c
to
f7bf30a
Compare
f7bf30a
to
6a41d8a
Compare
6a41d8a
to
313bfa4
Compare
313bfa4
to
4e27030
Compare
4e27030
to
7bee48d
Compare
7bee48d
to
b715583
Compare
Quality Gate passedIssues Measures |
This PR contains the following updates:
18.11.9
->18.19.68
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.