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
I have the trufflehog binary installed and executing the binary with the following flags returns several identified secrets within the directory. This was run in a directory that has our app code. trufflehog --no-verification --no-update --fail filesystem .
I tried to implement the trufflehog action to perform the same scan and return the same results using the following workflow:
The ls step was included to confirm that the checkout actions correctly clones our application code from the configured repository, however the trufflehog step returns the following:
No secrets are found whereas executing the binary locally identifies several secrets and presents them in the following format:
Found unverified result 🐷🔑❓
Detector Type: Postmark
Decoder Type: PLAIN
Raw result: d2589a75-83e8-4a5f-sjf9-37cc21a3449a
File: file/Controller/Company_Controller.php
Do you see any problem with the action implementation? Can anyone share examples that work?
The text was updated successfully, but these errors were encountered:
Hi There,
I have the trufflehog binary installed and executing the binary with the following flags returns several identified secrets within the directory. This was run in a directory that has our app code.
trufflehog --no-verification --no-update --fail filesystem .
I tried to implement the trufflehog action to perform the same scan and return the same results using the following workflow:
The
ls
step was included to confirm that the checkout actions correctly clones our application code from the configured repository, however the trufflehog step returns the following:No secrets are found whereas executing the binary locally identifies several secrets and presents them in the following format:
Do you see any problem with the action implementation? Can anyone share examples that work?
The text was updated successfully, but these errors were encountered: