Skip to content
Java CI with Maven

Potential fix for code scanning alert no. 73: Use of a broken or risky cryptographic algorithm #24

Sign in to view logs

Potential fix for code scanning alert no. 73: Use of a broken or risky cryptographic algorithm

Potential fix for code scanning alert no. 73: Use of a broken or risky cryptographic algorithm #24

Triggered via pull request February 4, 2026 17:00
@davewichersdavewichers
opened #5
alert-autofix-73
Status Success
Total duration 59s
Artifacts –

maven.yaml

on: pull_request
build
44s
build
Fit to window
Zoom out
Zoom in