I apologise in advance if I'm breaking any rules by opening this ticket.
TruffleHog Version
3.69.0
Trace Output
Unfortunately, cannot share a output due to the sensitive data I have in hands. I wanted to nevertheless report the bug or maybe get help in figuring out why this is happening.
Expected Behavior
As with any other entry in the JSON output, the composition of the JSON looks like this:
The output composition should be the the same for all detectors.
Actual Behavior
Seems the repository property is missing in the resulting JSON TruffleHog generates when custom regexes are configured. Cannot understand why exactly, if this is a known bug or something else, but since it seems to work for other detectors, then I must assume this is some sort of bug?
Steps to Reproduce
Set up custom regexes to run TruffleHog with.
Observe the detected secrets for CustomRegex do not contain the repository property in the Metadata key.
Observe all other detections do provide this data.
Environment
Running TruffleHog on MacOS M1 Sonoma 14.5
Using containers to run TruffleHog version 3.69.0.
I apologise in advance if I'm breaking any rules by opening this ticket.
TruffleHog Version
3.69.0
Trace Output
Unfortunately, cannot share a output due to the sensitive data I have in hands. I wanted to nevertheless report the bug or maybe get help in figuring out why this is happening.
Expected Behavior
As with any other entry in the JSON output, the composition of the JSON looks like this:
The output composition should be the the same for all detectors.
Actual Behavior
Seems the
repository
property is missing in the resulting JSON TruffleHog generates when custom regexes are configured. Cannot understand why exactly, if this is a known bug or something else, but since it seems to work for other detectors, then I must assume this is some sort of bug?Steps to Reproduce
CustomRegex
do not contain the repository property in the Metadata key.Environment
Additional Context
N/A
References
N/A