Would be handy to have a machine-parsable version of the output to be able to run this and get JSON back with the list of vulnerable files found. Then it can be consumed by other tools or written out in a report of the user's design.
Something like
log4j-detect.exe -d C:/path --json
Would be handy to have a machine-parsable version of the output to be able to run this and get JSON back with the list of vulnerable files found. Then it can be consumed by other tools or written out in a report of the user's design.
Something like