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

[Snyk] Upgrade org.projectlombok:lombok from 1.18.26 to 1.18.30 #173

Closed
wants to merge 2 commits into from

Conversation

wistefan
Copy link
Collaborator

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade org.projectlombok:lombok from 1.18.26 to 1.18.30.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released 2 months ago, on 2023-09-20.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Creation of Temporary File in Directory with Insecure Permissions
SNYK-JAVA-COMGOOGLEGUAVA-5710356
379/1000
Why? Has a fix available, CVSS 3.3
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@wistefan wistefan added the patch Indicates that the branch contains a bug fix label Aug 1, 2024
@wistefan wistefan closed this Aug 5, 2024
@wistefan wistefan deleted the snyk-upgrade-8b955d9494c499dc0fc7f7b5d4446b93 branch August 5, 2024 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch Indicates that the branch contains a bug fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants