chore(deps): bump com.github.spotbugs:spotbugs-maven-plugin from 4.8.6.5 to 4.8.6.6 in /jans-scim

[dependabot]

Bumps com.github.spotbugs:spotbugs-maven-plugin from 4.8.6.5 to 4.8.6.6.

Release notes

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

Spotbugs Maven Plugin 4.8.6.6

• Cleanup groovy code
• Cleanup character encoding
• Update deprecated maven calls
• Groovy moved to 4.0.24

Compatibility remains with 4.8.6 of spotbugs

Commits

• 9895d2e [maven-release-plugin] prepare release spotbugs-maven-plugin-4.8.6.6
• 028a1a3 Merge pull request #924 from hazendaz/next-up
• 1b6f4bf [ci] Gstring to string
• cf9ebd1 [ci] Run eclipse formatter against the code
• 62ddea0 Merge pull request #923 from hazendaz/charset
• 559b0ca [logging] Use correct quoting in log line
• f2baf85 [maven] Update deprecated code from current project call for reports plugin
• e5fd7e7 [groovy] Use less gstrings when not needed and sort parameter attributes
• 260a4da Merge pull request #922 from hazendaz/charset
• 192e8f2 Revert "[github] Bump to maven 4.0.0-beta-5"
• Additional commits viewable in compare view

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 <dependency name> 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dryrunsecurity]

DryRun Security Summary

The Janssen Project's jans-scim project updated the spotbugs-maven-plugin version in its pom.xml file, demonstrating ongoing commitment to code quality and security through static code analysis and monitoring tools.

Expand for full summary

Summary:

The provided code change is an update to the pom.xml file of the jans-scim project, which is part of the Janssen Project, an open-source identity and access management (IAM) platform. The change involves updating the version of the spotbugs-maven-plugin from 4.8.6.5 to 4.8.6.6. While this change is not directly related to the security of the application, the overall pom.xml file suggests that the Janssen Project team is following good practices for software development and security, such as using static code analysis tools and integrating with SonarCloud for code quality and security monitoring.

Files Changed:

• jans-scim/pom.xml: This file is the Maven configuration for the jans-scim project. The change updates the version of the spotbugs-maven-plugin from 4.8.6.5 to 4.8.6.6. The spotbugs-maven-plugin is a tool used to perform static code analysis, which can help identify potential security vulnerabilities in the codebase. The overall pom.xml file also indicates that the project is part of the Janssen Project, an open-source IAM platform, and that it uses various tools and practices for code quality and security, such as the jacoco-maven-plugin for code coverage reporting and integration with SonarCloud for code analysis.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

View PR in the DryRun Dashboard.