We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Scans of the most recent wait-for-port release are showing multiple vulnerabilities in the version of go that was used to build the binary.
wait-for-port
All can be resolved by updating to the latest go 1.21 version (1.21.11)
No high impact vulnerabilities reported in scanning of artifacts.
Above mentioned vulnerabilities
No response
The text was updated successfully, but these errors were encountered:
Closing this issue as these are all resolved in the v1.0.8 release from today which upgraded to go 1.22.4.
Sorry, something went wrong.
javsalgar
No branches or pull requests
What steps will reproduce the bug?
Scans of the most recent
wait-for-port
release are showing multiple vulnerabilities in the version of go that was used to build the binary.All can be resolved by updating to the latest go 1.21 version (1.21.11)
What is the expected behavior?
No high impact vulnerabilities reported in scanning of artifacts.
What do you see instead?
Above mentioned vulnerabilities
Additional information
No response
The text was updated successfully, but these errors were encountered: