Skip to content
Browse files

README: Add a brief mention of the evaluator

We still need proper docs as mentioned at #1236.

Signed-off-by: Sebastian Schuberth <>
  • Loading branch information...
sschuberth committed May 2, 2019
1 parent a3115a3 commit a838e811c6c60585ab35e7f6d64a70ae2271fe67
Showing with 10 additions and 1 deletion.
  1. +10 −1
@@ -37,7 +37,7 @@ The toolkit is envisioned to consist of the following libraries:
changes to the software project are required.
* [Downloader](#downloader) - fetches the source code based on the Analyzer's output.
* [Scanner](#scanner) - wraps existing copyright / license scanners to detect findings in local source code directories.
* *Evaluator* - evaluates results as OK or NOT OK against user-specified rules.
* [Evaluator](#evaluator) - evaluates results as OK or NOT OK against user-specified rules.
* *Advisor* * - retrieves security advisories based on Analyzer results.
* [Reporter](#reporter) - presents results in various formats (incl. `NOTICE` files), making it easy to identify
dependencies, licenses, copyrights and policy violations.
@@ -141,6 +141,15 @@ artifactory_storage:

<a name="evaluator">&nbsp;</a>


The evalutor is used to perform custom license policy checks on scan results. The rules to check against are implemented
via scripting. Currently, Kotlin script with a dedicated DSL is used for that, but support for other scripting languages
can be added as well. See [no_gpl_declared.kts](./evaluator/src/main/resources/rules/no_gpl_declared.kts) for a very
simple example of a rule written in Kotlin script which verifies that no dependencies that declare the GPL are used.

<a name="reporter">&nbsp;</a>


0 comments on commit a838e81

Please sign in to comment.
You can’t perform that action at this time.