You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
It would be great if we can include the trufflehog version in the output reports(both json and normal)
Problem to be Addressed
Given autoupdate is ON by default and fast releases happening in this project, when we are seeing trufflehog failures in our CI history (i.e. builds that ran like 3 days ago, 1 week ago etc) we are unable to say which exact version of trufflehog raised the given issue.
Description of the Preferred Solution
In the truffle hog result (both json and normal report) include a field which states which version of trufflehog found the issue
Community Note
Description
It would be great if we can include the trufflehog version in the output reports(both json and normal)
Problem to be Addressed
Given autoupdate is ON by default and fast releases happening in this project, when we are seeing trufflehog failures in our CI history (i.e. builds that ran like 3 days ago, 1 week ago etc) we are unable to say which exact version of trufflehog raised the given issue.
Description of the Preferred Solution
In the truffle hog result (both json and normal report) include a field which states which version of trufflehog found the issue
Additional Context
Current JSON report structure
Following is the current json report structure
Proposed json
The text was updated successfully, but these errors were encountered: