| **ERROR_ON_MISSING_EXEC_BIT** | If set to `false`, the `bash-exec` linter will report a warning if a shell script is not executable. If set to `true`, the `bash-exec` linter will report an arror instead.| `false` |
Please be aware that any config file specified is relative to `$LINTER_RULES_PATH`, so you have to put **all your
templating** under the path specified. If you are curious to know what are the *default templates* files for your
linters, they are all available in the [`TEMPLATES`](https://github.com/github/super-linter/tree/master/TEMPLATES)
folder
#### Enable or disable linters
!!! info "Note about `VALIDATE_[LANGUAGE]` variables from super-linter [README](https://github.com/github/super-linter#environment-variables){:target="_blank"}"
With the default configuration, this job will fail if errors are detected.
With the default configuration, this job will fail if detected errors are in severity `MEDIUM`,`HIGH`,`CRITICAL`.
It's the recommended configuration to reduce security risks in your
software. You can disable this behaviour by setting the value `0` to the
variable `TRIVY_EXIT_CODE`.
software. You can disable this behaviour by emptying the value of the
variable `TRIVY_EXIT_ON_SEVERITY`.
## How to use it
@@ -36,7 +36,8 @@ vulnerability detection capabilities are available in its official
|:-|:-|:-
| `TRIVY_VERSION`<imgwidth=450/> | Version of trivy to use. Releases version are available [here](https://github.com/aquasecurity/trivy/releases){:target="_blank"} | `0.9.2` |
| `TRIVY_SEVERITY` | Severities of vulnerabilities to be displayed | `UNKNOWN`,`LOW`,`MEDIUM`,`HIGH`,`CRITICAL`|
| `TRIVY_EXIT_CODE` | Exit code when vulnerabilities were found | 1 |
| `TRIVY_EXIT_ON_SEVERITY` | Severities of vulnerabilities for the job to fail at | `MEDIUM`,`HIGH`,`CRITICAL`|
| `TRIVY_EXIT_CODE` | Exit code when vulnerabilities were found | 0 |
| `TRIVY_VULN_TYPE` | List of vulnerability types | os,library |
| `TRIVY_OUTPUT` | Output file name | junit-report.xml |