Set Gradle verification to check the dependency have been compromised #1410
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What I have done and why
Set Gradle verification.
From this documentation
Gradle can check dependencies' checksum in build time, and verify that dependencies have been compromised.
I set Gradle option for just warning when checksum throw error.
If you want to make new
verification-metadata.xml
, run thisgradle --write-verification-metadata sha256 check
How I'm testing it
Choose at least one: