From 5848cea47face2eff6c2ddd105492f9892733f0c Mon Sep 17 00:00:00 2001 From: Peter Jaap Blaakmeer Date: Sat, 19 Nov 2022 17:25:44 +0100 Subject: [PATCH] Added docs --- doc/tasks/securitychecker/enlightn.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/tasks/securitychecker/enlightn.md b/doc/tasks/securitychecker/enlightn.md index 3c51ccca..6c0fc09e 100644 --- a/doc/tasks/securitychecker/enlightn.md +++ b/doc/tasks/securitychecker/enlightn.md @@ -19,6 +19,7 @@ grumphp: securitychecker_enlightn: lockfile: ./composer.lock run_always: false + allow-list: [] ``` **lockfile** @@ -32,3 +33,9 @@ If your `composer.lock` file is located in an exotic location, you can specify t *Default: false* When this option is set to `false`, the task will only run when the `composer.lock` file has changed. If it is set to `true`, the `composer.lock` file will be checked on every commit. + +**allow-list** + +*Default: empty array* + +When an array is set, these values (vulnerabilities) will be passed on to the security checker to ignore the given values. See [the enlightn/security-checker docs](https://github.com/enlightn/security-checker#allow-vulnerabilities) for more information.