JanssenProject / jans

An open source enterprise digital identity platform for CIAM or workforce... Janssen is a distribution of standards-based, developer friendly, components that are engineered to work together in any cloud. #OAuth #OpenID #FIDO
https://docs.jans.io
Apache License 2.0
457 stars 74 forks source link

chore(deps): bump com.github.spotbugs:spotbugs-maven-plugin from 4.7.3.4 to 4.8.6.0 in /jans-orm #8784

Closed dependabot[bot] closed 3 weeks ago

dependabot[bot] commented 3 months ago

Bumps com.github.spotbugs:spotbugs-maven-plugin from 4.7.3.4 to 4.8.6.0.

Release notes

Sourced from com.github.spotbugs:spotbugs-maven-plugin's releases.

Spotbugs Maven Plugin 4.8.6.0

Support spotbugs 4.8.6

Spotbugs Maven Plugin 4.8.5.0

  • Support spotbugs 4.8.5.0
  • Dependency and plugin general updates
  • Maven wrapper update to 3.3.1

Spotbugs Maven Plugin 4.8.4.0

User

  • Support spotbugs 4.8.4
  • library updates / plugin updates
  • Supports jdk 23
  • Require maven 3.6.3 per maven deprecation

Build

  • Update renovate config
  • Update GHA for adjustments to maven/java
  • Drop modernizer plugin back to 2.7.0 as it was restricted to maven 3.9.5 (will be fixed on next release)

Spotbugs Maven Plugin 4.8.3.1

  • Support for spotbugs 4.8.3
  • Bump groovy to 4.0.18
  • Bump slf4j to 2.0.12
  • Bump commons codec to 1.16.1

Spotbugs Maven Plugin 4.8.3.0

This release is much larger than most, all IT tests are good to go. Given scope of changes, if any issues seen, please raise ticket so we can quickly address. A lot was done here to fix-up lazy groovy usage.

Consumer

  • Support for spotbugs 4.8.3
  • library updates
  • Add 'noClassOk' option (untested)
  • Stop overusing 'def' from groovy and use concrete types
  • Many plexus to standard java usage
  • Switch 'Boolean' to 'boolean' for parameters
  • Remove long deprecated and not actually used spotbugsXmlOutput
  • Switch to using buffered writer
  • Drop supporting 2005 version of jxr-maven-plugin
  • Add support for usage of classifier (untested)
  • Add better logging when plugin skipped
  • Cleanup property usage and remove unused properties

Build

  • For integration tests switch to jakarta namespace
  • Cleanup site

... (truncated)

Commits
  • be70f9e [maven-release-plugin] prepare release spotbugs-maven-plugin-4.8.6.0
  • 9614424 [pom] Bump remainder of spotbugs items to 4.8.6
  • d3b7c91 Merge pull request #829 from spotbugs/renovate/spotbugsversion
  • e8f5f5a Merge pull request #831 from spotbugs/renovate/javaparserversion
  • f65089a Update dependency com.github.javaparser:javaparser-core to v3.26.1
  • 69e2c80 Update dependency com.github.spotbugs:spotbugs to v4.8.6
  • 816edbe Merge pull request #827 from spotbugs/renovate/maven-3.x
  • 3507e6f Merge pull request #828 from spotbugs/renovate/mavenversion
  • 150ae87 Update mavenVersion to v3.9.8
  • e0c83ff Update dependency maven to v3.9.8
  • Additional commits viewable in compare view


Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
\nPlease check the below before submitting your PR. The PR will not be merged if there are no commits that start with `docs:` to indicate documentation changes or if the below checklist is not selected.\n- [x] **I confirm that there is no impact on the docs due to the code changes in this PR.** > **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
dryrunsecurity[bot] commented 3 months ago

Hi there :wave:, @dryrunsecurity here, below is a summary of our analysis and findings.

DryRun Security Status Findings
Configured Codepaths Analyzer :white_check_mark: 0 findings
Server-Side Request Forgery Analyzer :white_check_mark: 0 findings
SQL Injection Analyzer :white_check_mark: 0 findings
Authn/Authz Analyzer :white_check_mark: 0 findings
Sensitive Files Analyzer :grey_exclamation: 1 finding
IDOR Analyzer :white_check_mark: 0 findings
Secrets Analyzer :white_check_mark: 0 findings

[!Note] :green_circle: Risk threshold not exceeded.

Change Summary (click to expand) The following is a summary of changes in this pull request made by me, your security buddy :robot:. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective. **Summary:** The provided code change is an update to the `spotbugs-maven-plugin` version in the `pom.xml` file of the `jans-orm` project. The previous version `4.7.3.4` is being updated to `4.8.6.2`. From an application security perspective, this change is generally positive as it updates the SpotBugs plugin to a newer version. Updating the plugin can provide benefits such as security fixes, bug fixes, and feature improvements, which can help improve the overall security and quality of the `jans-orm` project. **Files Changed:** - `jans-orm/pom.xml`: This file has been updated to change the version of the `spotbugs-maven-plugin` from `4.7.3.4` to `4.8.6.2`. SpotBugs is a static code analysis tool that helps identify potential security vulnerabilities and other issues in Java applications. Updating the plugin to a newer version can provide security fixes, bug fixes, and feature improvements, which can enhance the security and quality of the `jans-orm` project.

Powered by DryRun Security

dryrunsecurity[bot] commented 2 months ago

DryRun Security Summary

The provided code change updates the spotbugs-maven-plugin version in the pom.xml file, which is a positive step towards improving the overall code quality and security of the application by leveraging a static code analysis tool.

Expand for full summary
**Summary:** The provided code change updates the version of the `spotbugs-maven-plugin` from `4.7.3.4` to `4.8.6.2` in the `pom.xml` file. This plugin is used for static code analysis, specifically to detect potential bugs in the Java code. From an application security perspective, this change is generally a positive one, as it indicates that the project is keeping its dependencies up-to-date and taking measures to improve the overall code quality and security. The SpotBugs tool, which is used by this plugin, can help identify a variety of security vulnerabilities, such as injection flaws, broken authentication and session management issues, cross-site scripting (XSS) vulnerabilities, and security misconfigurations. The update to a newer version of the `spotbugs-maven-plugin` may also include bug fixes, performance improvements, and support for newer versions of Java, which can further enhance the security and reliability of the application. **Files Changed:** - `jans-orm/pom.xml`: The code change in this file updates the version of the `spotbugs-maven-plugin` from `4.7.3.4` to `4.8.6.2`. This is a positive change, as it indicates that the project is taking steps to improve the overall code quality and security by leveraging a well-established static code analysis tool.

Code Analysis

We ran 7 analyzers against 1 file and 1 analyzer had findings. 6 analyzers had no findings.

Analyzer Findings
Sensitive Files Analyzer 1 finding

Riskiness

:green_circle: Risk threshold not exceeded.

View PR in the DryRun Dashboard.

dependabot[bot] commented 3 weeks ago

Superseded by #9380.