orcasecurity/Orca Security - Secret Detection (Git Repos)

Configures Orca CLI to run secrets scan on your code

View on GitHub

Trust Signals

Scorecard Score
Scorecard 4–6scored Jul 6, 2026
Maintenance Recency
Maintainedlast commit Feb 6, 2025
License
Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned
uses: orcasecurity/shiftleft-secrets-action@5d7e24bc32e40bac7f49bf1957171d3ec49e9a9e # v1.0.5

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
api_tokenOrca API Token used for Authenticationyes
exit_codeExit code for failed execution due to policy violationsno
no_colorDisable color outputnofalse
project_keyProject Key nameyes
silentDisable logs and warnings outputnofalse
disable_err_reportSuppress error reporting to the monitoring platformnofalse
max_secretMaximum secrets that can be found, when reaching this number secret scan will stopno
num_cpuNumber of logical CPUs to be used for secret scanning (default 10)no
pathPath or directory to scanno.
disable_git_scanDisable Git scannofalse
ignore_git_history_baselineRun full history scanno
from_commitThe commit to scan fromno
to_commitThe commit to scan tono
exceptions_filepathExceptions YAML file path.no
formatFormat for displaying the resultsnotable
outputOutput directoryno
timeoutSet the maximum duration for the CLI execution. valid time units ("s", "m", "h")no
show_failed_issues_onlyShow only failed issues in CLI resultsnofalse
console_outputPrints results to console in the provided format (only when --output is provided)notable
configPath to the configuration file (json, yaml or toml)no
show_annotationsShow GitHub annotations on pull requestsnotrue
debugDebug modenofalse
disable_active_verificationDisable active verificationnofalse
log_pathThe directory path to specify where the logs should be written to on debug mode. Default to the current working directoryno
namedescription
exit_codeThe exit code of the scan