Included in maven. Automatically verified at build time or validate
If configured to fail on error plugins will require being recorded into the trusted checksums
Minimal fileformat
Missing BOM information
Missing ENV information (such as java and maven version)
Both
Are independent of ordering of dependencies/checksums
Are not locked down to specific Java version (can be generated with Java 17 and tested with Java 21 without false triggers)
The main thing missing from Trusted Checksums is the ability to download the specific versions specified. If a version range is specified some manual work is required to check the specific version of the jar and specify that one in the pom.xml.
Suggestion: Maven lockfile could (maybe an optional parameter) setup the project to use trusted checksums.
Test on maven-lockfile
When run on the maven-lockfile project the following results are obtained.
Trusted Checksums recorded 1222 checksums, where 779 are checksums for .pom files.
Maven Lockfile recorded 300 checksums.
All checksums recorded in the lockfile are also recorded in the trusted checksums.
These checksums (filtered to only include jars) are in Trusted Checksums but missing in the lockfiles:
Features
Maven-Lockfile
Trusted Checksums
Both
The main thing missing from Trusted Checksums is the ability to download the specific versions specified. If a version range is specified some manual work is required to check the specific version of the jar and specify that one in the pom.xml.
Suggestion: Maven lockfile could (maybe an optional parameter) setup the project to use trusted checksums.
Test on maven-lockfile
When run on the maven-lockfile project the following results are obtained.
Trusted Checksums recorded 1222 checksums, where 779 are checksums for
.pom
files. Maven Lockfile recorded 300 checksums.All checksums recorded in the lockfile are also recorded in the trusted checksums.
These checksums (filtered to only include jars) are in Trusted Checksums but missing in the lockfiles: