Skip to content

Update all dependencies - #70

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all
Open

Update all dependencies#70
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all

Conversation

@renovate

@renovate renovate Bot commented Mar 16, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
actions/checkout action major v6v7 age adoption passing confidence
actions/setup-java action major v5v6 age adoption passing confidence
org.postgresql:postgresql (source) build patch 42.7.1042.7.12 age adoption passing confidence
org.mockito:mockito-core test minor 5.22.05.23.0 age adoption passing confidence
org.springdoc:springdoc-openapi-starter-webmvc-ui (source) compile minor 3.0.23.1.0 age adoption passing confidence
com.nimbusds:oauth2-oidc-sdk compile minor 11.3411.38.2 age adoption passing confidence
org.flywaydb:flyway-maven-plugin build major 12.0.313.4.0 age adoption passing confidence
com.github.gantsign.maven:ktlint-maven-plugin build minor 3.5.03.7.1 age adoption passing confidence
org.apache.maven.plugins:maven-enforcer-plugin (source) build patch 3.6.23.6.3 age adoption passing confidence
org.openapitools:openapi-generator-maven-plugin build minor 7.20.07.25.0 age adoption passing confidence
org.springframework.boot:spring-boot-starter-parent (source) parent minor 4.0.34.1.1 age adoption passing confidence

pgjdbc: Unbounded PBKDF2 iterations in SCRAM authentication allows CPU exhaustion DoS

CVE-2026-42198 / GHSA-98qh-xjc8-98pq

More information

Details

Summary

pgjdbc is vulnerable to a client-side denial of service during SCRAM-SHA-256 authentication.

Impact

A malicious server can instruct the driver to perform SCRAM authentication with a very large iteration count.
With a large enough value, the client spends an unbounded amount of CPU time inside PBKDF2 before authentication can fail.
A single attempt ties up a CPU core. Repeated or concurrent attempts exhaust client CPU and can wedge connection pools.

In affected versions, loginTimeout did not fully mitigate this problem. When loginTimeout expired, the caller could stop waiting, but the worker thread performing the connection attempt could continue running and burning CPU inside the SCRAM PBKDF2 computation.

This issue affects availability. It does not provide authentication bypass, privilege escalation, or direct password disclosure.

A user is vulnerable when all of the following are true:

  1. The connection uses SCRAM-SHA-256 authentication.
  2. The client reaches a malicious, compromised, or attacker-controlled PostgreSQL endpoint.
  3. That endpoint sends a very large SCRAM PBKDF2 iteration count in the server-first-message.

In practice, that can happen in these situations:

  • the application lets end users or tenants supply their own database connection details (as in many BI, reporting, analytics, ETL, and low-code platforms), so a user can point the shared client host at a server they control
  • the application accepts connection strings, hostnames, or JDBC URLs from user input, configuration uploaded by users, or other untrusted sources
  • the application is configured to connect to a PostgreSQL server that is itself malicious or later becomes compromised
  • the application connects through an untrusted proxy, relay, tunnel, bastion, or connection-pooling service that can act as the PostgreSQL server
  • an attacker can redirect the client to a fake PostgreSQL endpoint by manipulating DNS, service discovery, Kubernetes service resolution, /etc/hosts, environment variables, or similar indirection
  • an active network attacker on the path can impersonate the server because the connection does not strongly verify server identity (for example, sslmode lower than verify-full, or trusting a CA that signs hosts outside the operator's control)

The issue is more damaging when the application uses connection retries, many parallel connection attempts, or loginTimeout and assumes the timeout fully stops the work.

Patches

The patch introduces a new connection property, scramMaxIterations, with a default of 100K. The client now rejects SCRAM server messages that advertise more PBKDF2 iterations than the configured cap before starting the PBKDF2 computation begins.

Workarounds

Until a patched version of pgjdbc is deployed, the following measures reduce exposure:

  1. Only connect to trusted PostgreSQL servers whose identity is verified.
    Connect only to trusted PostgreSQL servers, and verify server identity with TLS using sslmode=verify-full and a trusted CA.
    TLS without certificate and hostname verification is not sufficient as an active network attacker can still impersonate the server.

  2. Do not rely on loginTimeout as a complete mitigation on unpatched versions.
    On affected versions, loginTimeout can stop the waiting caller while the worker thread continues spending CPU.

  3. Avoid SCRAM on untrusted or interceptable connection paths.
    For those paths, use an authentication method that does not let the server choose a SCRAM PBKDF2 iteration count.

  4. Reduce blast radius operationally.
    Limit parallel connection attempts, add retry backoff, isolate connection establishment in a separate worker or process when possible, and apply CPU or container limits where appropriate.

  5. On trusted servers you control, keep SCRAM iteration counts at ordinary values.
    This does not defend against an attacker-controlled server, but it avoids unnecessary client cost when talking to legitimate servers.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


PostgreSQL JDBC Driver: Silent channel-binding authentication downgrade via unsupported certificate algorithms

CVE-2026-54291 / GHSA-j92g-9f8w-j867

More information

Details

Impact

channelBinding=require connections can be silently downgraded from SCRAM-SHA-256-PLUS (with channel binding) to plain SCRAM-SHA-256 (without it), losing the man-in-the-middle protection the setting is meant to guarantee. An attacker who can intercept the TLS connection triggers the downgrade with a certificate whose signature algorithm has no tls-server-end-point channel-binding hash. Examples are Ed25519, Ed448, and post-quantum algorithms.

Two issues combine in releases 42.7.4 through 42.7.11:

  1. The bundled com.ongres.scram:scram-client (3.1 or 3.2) returns an empty byte array instead of failing when it cannot derive the binding hash for such a certificate. This is the library issue tracked as GHSA-p9jg-fcr6-3mhf.
  2. pgJDBC does not enforce channelBinding=require where it matters. ScramAuthenticator checks only that the server advertised a -PLUS mechanism; it neither rejects the empty binding nor checks that the negotiated mechanism uses channel binding. The connection therefore downgrades silently, and would do so even against a fixed scram-client, because the missing enforcement is in pgJDBC's own code.

Only connections that set channelBinding=require are affected. Under the default prefer policy, and under allow or disable, falling back to plain SCRAM is the documented behaviour. Releases before 42.7.4 are unaffected, because they do not support channel binding.

Patches

Fixed in pgJDBC 42.7.12. pgJDBC now enforces channel binding in its own code, independently of the scram-client version:

  • Under channelBinding=require, it fails the connection when no channel-binding data can be extracted from the server certificate, instead of passing an empty value to the SCRAM client. The error names the certificate signature algorithm.
  • After negotiation, it requires the selected mechanism to use channel binding (a -PLUS mechanism) whenever channelBinding=require is set, regardless of how negotiation resolved.

Upgrade to 42.7.12 or later.

Workarounds

No pgJDBC setting restores channel-binding enforcement on an affected release; upgrading is the fix.

If you cannot upgrade immediately, verify the server certificate at the TLS layer so that a man-in-the-middle cannot present a substitute certificate. Set sslmode=verify-full with a truststore that contains only your server's CA. This defence is independent of channel binding and blocks the same attacker. Connections that rely on channelBinding=require in place of certificate verification have no equivalent workaround and should upgrade.

References

Severity

  • CVSS Score: 8.2 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

actions/checkout (actions/checkout)

v7.0.1

Compare Source

v7.0.0

Compare Source

v7

Compare Source

v6.1.0

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

actions/setup-java (actions/setup-java)

v6.0.0

Compare Source

v6

Compare Source

v5.7.0

Compare Source

v5.6.0

Compare Source

What's Changed

Full Changelog: actions/setup-java@v5...v5.6.0

v5.5.0

Compare Source

v5.4.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-java@v5...v5.4.0

v5.3.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-java@v5...v5.3.0

v5.2.0

Compare Source

What's Changed
Enhancement
Documentation Changes
Dependency Updates
New Contributors

Full Changelog: actions/setup-java@v5...v5.2.0

v5.1.0

Compare Source

What's Changed
New Features
Bug Fixes & Improvements
Documentation changes
Dependency updates
New Contributors

Full Changelog: actions/setup-java@v5...v5.1.0

pgjdbc/pgjdbc (org.postgresql:postgresql)

v42.7.12

Security
  • fix: Enforce SCRAM channel-binding policy and prevent silent downgrade.
    Under channelBinding=require, the driver silently downgraded from SCRAM-SHA-256-PLUS (with channel binding) to plain SCRAM-SHA-256 (without it) when the server presented a certificate whose signature algorithm has no tls-server-end-point channel-binding hash (e.g. Ed25519, Ed448, or post-quantum algorithms). An attacker who can intercept the TLS connection could exploit this to strip channel-binding protection.
    The fix enforces channel binding in the driver's own code: it now fails the connection when no binding data can be extracted, and verifies the negotiated mechanism uses channel binding (-PLUS) when require is set.
    Only connections that set channelBinding=require are affected. The default prefer policy and releases before 42.7.4 (which introduced channel-binding support) are unaffected.
    See the Security Advisory for more detail.
    The following CVE-2026-54291 has been issued.

v42.7.11

Security
  • fix: Limit SCRAM PBKDF2 iterations accepted from the server.
    pgjdbc was vulnerable to a client-side denial of service in SCRAM-SHA-256 authentication, where a malicious or compromised PostgreSQL server could specify an extremely large PBKDF2 iteration count, causing the client to consume unbounded CPU and potentially exhaust connection pools. The fix introduces a new scramMaxIterations connection property (defaulting to 100,000) to cap iteration counts before computation begins.
    See the Security Advisory for more detail.
    The following CVE-2026-42198 has been issued.
Added
  • feat: implement require_auth connection property, aligning with libpq behavior PR #​3895
Changed
  • chore: replace Appveyor CI with ikalnytskyi/action-setup-postgres PR #​3966
  • chore: upgrade Gradle to v9 PR #​3978
Fixed
  • fix: ensure extended protocol messages end with Sync message PR #​3728
  • fix: enable cursor-based fetching in extended protocol when transaction started via SQL command PR #​3996
  • fix: retry with SSL on IOException when sslMode=ALLOW PR #​3973
  • fix: make sure the driver honours connectTimeout when retrying the connection PR #​3968
  • fix: allow fallback to non-SSL connection when sslMode=prefer and sslResponseTimeout kicks in PR #​3968
  • fix: catch SecurityException from setContextClassLoader on ForkJoinPool workers PR #​3962
  • fix: use compareTo for LogSequenceNumber comparison to handle unsigned values correctly PR #​3961
  • fix: release COPY lock on IOException to prevent connection hang PR #​3957
  • fix: return jsonb as PGObject instead of String PR #​3956
  • fix: align SSL key file permission check with libpq PR #​3952
  • fix: guard connection closed flag with a reentrant lock to protect against concurrent close PR #​3905
mockito/mockito (org.mockito:mockito-core)

v5.23.0

NOTE: Breaking change for Android

The mockito-android artifact has a breaking change: tests now require a device or emulator based on API 28+ (Android P). This is to enable new support for mocking Kotlin classes. See #​3788 for more details.


Changelog generated by Shipkit Changelog Gradle Plugin

5.23.0
  • 2026-03-11 - 6 commit(s) by Brice Dutheil, Joshua Selbo, Philippe Kernevez
  • Replace mockito-android mock maker implementation with dexmaker-mockito-inline (#​3792)
  • Fix StackOverflowError with AbstractList after using mockSingleton (#​3790)
  • Mark parameters of Mockito.when @Nullable (#​3503)
springdoc/springdoc-openapi (org.springdoc:springdoc-openapi-starter-webmvc-ui)

v3.1.0

Added
  • #​3269 – Add mechanism to disable nullable for Kotlin properties
  • Allow request-specific Swagger UI index transformation
Changed
  • Upgrade Spring Boot to version 4.1.0
  • Upgrade Spring AI to version 2.0.0
  • Upgrade swagger-core to version 2.2.52
  • Upgrade swagger-ui to version 5.32.11
  • #​3307 – Act upon SonarQube warnings
  • #​3306 – Act upon SonarQube warnings
Fixed
  • #​3304 – Kotlin parent class's field is not properly marked as nullable
  • #​3294 – Duplicated path getting swagger-config
  • #​3293 – Inconsistent OpenAPI schema naming with SNAKE_CASE: some Java record fields remain camelCase
  • #​3292 – Make WebProperties and WebMvcProperties optional in SwaggerConfig
  • #​3284 – Upgrade swagger-core from version 2.2.48 to 2.2.49
  • #​3282 – Preserve version from nest() predicate across all routes in nest
  • #​3281 – Stabilize Spring Data Page schema property order
  • #​3274 – Description disappears from the generated json after upgrade to 3.0.3
  • #​3270 – Validation annotation of ParameterObject property applied to PathVariable with the same name, even in unrelated endpoints
  • #​3266 – Upgrade swagger-core from version 2.2.47 to 2.2.48
  • #​3263 – Null key for a Map not allowed in JSON

v3.0.3

Compare Source

Added
  • #​3246 – Add Springdoc OpenAPI MCP (Model Context Protocol) support
  • #​3256 – Auto-set nullable: true for Kotlin nullable types in schema properties
  • #​3239 – Add support for the @Range constraint validation annotation
  • #​3244 – Handle default values for LocalDate
Changed
  • Upgrade Spring Boot to version 4.0.5
  • Upgrade swagger-core to version 2.2.47
  • Upgrade swagger-ui to version 5.32.2
  • #​3260@ConditionalOnClass(HateoasProperties.class) in SpringDocHateoasConfiguration
  • Forwards all MCP non-transport headers to downstream methods
  • Dynamically resolve the base path from window.location.pathname for MCP UI
Fixed
  • #​3258 – Setting API Version Required when using WebFlux breaks the Swagger UI
  • #​3259 – Annotated Generic properties getting applied to sibling properties
  • #​3255Direction enum: fixed visibility scope of group order so that setGroupsOrder method can be used
  • #​3247 – Preserve YAML group URLs in Swagger UI
  • #​3245 – Upgrade swagger-core from version 2.2.43 to 2.2.45
  • #​3235PropertyResolverUtils retains a JsonNode when reading an ExtensionProperty annotation
  • #​3226 – Propagate JsonView context when resolving Page<T> schema
connect2id/oauth-2.0-sdk-with-openid-connect-extensions (com.nimbusds:oauth2-oidc-sdk)

v11.38.2

Compare Source

v11.38.1

Compare Source

v11.38

Compare Source

v11.37.2

Compare Source

v11.37.1

Compare Source

v11.37

Compare Source

v11.36

Compare Source

v11.35

Compare Source

gantsign/ktlint-maven-plugin (com.github.gantsign.maven:ktlint-maven-plugin)

v3.7.1

Compare Source

Changes:

v3.7.0

Compare Source

Enhancement:

  • #​717: Update ktlint to 1.8.0 an

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.


This change is Reviewable

@renovate
renovate Bot requested a review from a team March 16, 2026 02:37
@github-actions

github-actions Bot commented Mar 16, 2026

Copy link
Copy Markdown

Dependency Review

The following issues were found:
  • ✅ 0 vulnerable package(s)
  • ✅ 0 package(s) with incompatible licenses
  • ✅ 0 package(s) with invalid SPDX license definitions
  • ⚠️ 2 package(s) with unknown licenses.
See the Details below.

License Issues

.github/workflows/ktlint.yml

PackageVersionLicenseIssue Type
actions/checkout7.*.*NullUnknown License
actions/setup-java6.*.*NullUnknown License
Allowed Licenses: CC0-1.0, CC-BY-4.0, Unlicense, WTFPL, 0BSD, MIT, Apache-2.0, ISC, BSD-2-Clause, BSD-3-Clause, Zlib, MPL-1.1, MPL-2.0, CDDL-1.0, EPL-1.0, EPL-2.0, CECILL-2.1, LGPL-2.1-only, LGPL-2.1-or-later, LGPL-3.0-only, LGPL-3.0-or-later, EUPL-1.0, EUPL-1.1, EUPL-1.2, AAL, AFL-3.0, Apache-1.1, APL-1.0, APSL-2.0, Artistic-1.0-Perl, Artistic-2.0, BlueOak-1.0.0, BSL-1.0, CATOSL-1.1, CPAL-1.0, CUA-OPL-1.0, ECL-2.0, EFL-2.0, Entessa, EUDatagrid, Fair, LPPL-1.3c, LPL-1.02, MirOS, Motosoto, Multics, NASA-1.3, NCSA, NTP, Naumen, Nokia, PostgreSQL, PSF-2.0, RPSL-1.0, RSCPL, SimPL-2.0, Sleepycat, SPL-1.0, VSL-1.0, W3C, W3C-20150513, Xnet, ZPL-2.0
Excluded from license check: pkg:githubactions/trufflesecurity/trufflehog, pkg:npm/knex, pkg:npm/mapbox-gl

OpenSSF Scorecard

PackageVersionScoreDetails
actions/actions/checkout 7.*.* 🟢 7
Details
CheckScoreReason
Maintained🟢 1024 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Code-Review🟢 10all changesets reviewed
Binary-Artifacts🟢 10no binaries found in the repo
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Fuzzing⚠️ 0project is not fuzzed
Packaging⚠️ -1packaging workflow not detected
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Pinned-Dependencies🟢 3dependency not pinned by hash detected -- score normalized to 3
Security-Policy🟢 9security policy file detected
SAST🟢 10SAST tool is run on all commits
Branch-Protection🟢 6branch protection is not maximal on development and all release branches
actions/actions/setup-java 6.*.* 🟢 5.4
Details
CheckScoreReason
Maintained🟢 1030 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 3Found 9/26 approved changesets -- score normalized to 3
Binary-Artifacts🟢 10no binaries found in the repo
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Packaging⚠️ -1packaging workflow not detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
License🟢 10license file detected
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Signed-Releases⚠️ -1no releases found
Fuzzing⚠️ 0project is not fuzzed
Security-Policy🟢 9security policy file detected
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST🟢 10SAST tool is run on all commits
maven/com.github.gantsign.maven:ktlint-maven-plugin 3.7.1 🟢 3.1
Details
CheckScoreReason
Code-Review⚠️ 0Found 1/14 approved changesets -- score normalized to 0
Maintained⚠️ 00 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts🟢 10no binaries found in the repo
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Security-Policy⚠️ 0security policy file not detected
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Packaging⚠️ -1packaging workflow not detected
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
maven/com.nimbusds:oauth2-oidc-sdk 11.38.2 UnknownUnknown
maven/org.apache.maven.plugins:maven-enforcer-plugin 3.6.3 🟢 5.6
Details
CheckScoreReason
Packaging⚠️ -1packaging workflow not detected
Security-Policy🟢 10security policy file detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Code-Review🟢 5Found 9/17 approved changesets -- score normalized to 5
Maintained🟢 1018 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
maven/org.flywaydb:flyway-maven-plugin 13.4.0 UnknownUnknown
maven/org.mockito:mockito-core 5.23.0 🟢 7.3
Details
CheckScoreReason
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Code-Review🟢 9Found 17/18 approved changesets -- score normalized to 9
Security-Policy🟢 9security policy file detected
Maintained🟢 1016 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions🟢 10GitHub workflow tokens follow principle of least privilege
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
License🟢 10license file detected
Fuzzing⚠️ 0project is not fuzzed
Branch-Protection⚠️ -1internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Signed-Releases⚠️ -1no releases found
Packaging🟢 10packaging workflow detected
Binary-Artifacts🟢 10no binaries found in the repo
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
maven/org.openapitools:openapi-generator-maven-plugin 7.25.0 🟢 5.7
Details
CheckScoreReason
Code-Review🟢 9GitHub code reviews found for 28 commits out of the last 30 -- score normalized to 9
Maintained🟢 1030 commit(s) out of 30 and 4 issue activity out of 30 found in the last 90 days -- score normalized to 10
CII-Best-Practices⚠️ 0no badge detected
Vulnerabilities🟢 10no vulnerabilities detected
Signed-Releases⚠️ -1no releases found
Branch-Protection🟢 3branch protection is not maximal on development and all release branches
Dependency-Update-Tool🟢 10update tool detected
Packaging⚠️ -1no published package detected
License🟢 10license file detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Token-Permissions⚠️ 0non read-only tokens detected in GitHub workflows
Security-Policy⚠️ 0security policy file not detected
Pinned-Dependencies⚠️ -1internal error: error parsing shell code: modules/openapi-generator/src/main/resources/bash/Dockerfile.mustache:1:9: reached EOF without closing quote '
Fuzzing⚠️ 0project is not fuzzed
Binary-Artifacts⚠️ 0binaries present in source code
maven/org.postgresql:postgresql 42.7.12 🟢 7.8
Details
CheckScoreReason
Dependency-Update-Tool🟢 10update tool detected
Maintained🟢 1030 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Security-Policy🟢 10security policy file detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
Code-Review🟢 8Found 24/30 approved changesets -- score normalized to 8
Token-Permissions🟢 9detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies🟢 9dependency not pinned by hash detected -- score normalized to 9
Vulnerabilities🟢 100 existing vulnerabilities detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
SAST🟢 10SAST tool is run on all commits
Binary-Artifacts🟢 10no binaries found in the repo
License🟢 10license file detected
Signed-Releases⚠️ 11 out of the last 5 releases have a total of 1 signed artifacts.
Fuzzing⚠️ 0project is not fuzzed
Branch-Protection🟢 3branch protection is not maximal on development and all release branches
CI-Tests🟢 1030 out of 30 merged PRs checked by a CI test -- score normalized to 10
Contributors🟢 10project has 35 contributing companies or organizations
maven/org.springdoc:springdoc-openapi-starter-webmvc-ui 3.1.0 UnknownUnknown

Scanned Files

  • .github/workflows/ktlint.yml
  • pom.xml

@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 205da9e to 130d056 Compare March 24, 2026 09:05
@renovate
renovate Bot force-pushed the renovate/all branch 4 times, most recently from 0c7e11d to ae7c54e Compare March 31, 2026 20:47
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from c27aca0 to bb5227c Compare April 12, 2026 00:37
@renovate
renovate Bot force-pushed the renovate/all branch 4 times, most recently from 75cc4f1 to 6f2211d Compare April 28, 2026 23:16
@renovate
renovate Bot force-pushed the renovate/all branch from 6f2211d to bed38e3 Compare May 6, 2026 08:23
@renovate renovate Bot changed the title Update all dependencies Update versions.postgresql [SECURITY] May 6, 2026
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 1baf893 to 9c3371c Compare May 12, 2026 17:30
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from eeeab84 to 273b751 Compare May 21, 2026 10:59
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from e51830f to 67eba4e Compare June 4, 2026 16:26
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from a88be56 to ddffb01 Compare June 10, 2026 19:34
@renovate renovate Bot changed the title Update versions.postgresql [SECURITY] Update all dependencies Jun 18, 2026
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from e9b8120 to b1f6928 Compare July 10, 2026 16:42
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 6250190 to 186d3fb Compare July 23, 2026 16:48
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 8e18774 to cadb3bc Compare August 2, 2026 01:06
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from e32d3a1 to a060089 Compare August 24, 2026 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants