Include an automatic security check after the build and before the push.
https://github.com/lukebond/microscanner-wrapper

The more dependency versions are mentioned in a Docker tag, the safer is its usage.
Tagging Docker image can thus get quite confusing when all relevant tool and dependency versions are to be included (e.g., alpine, git, docker and compose) for a Docker image.

That challenge is to be solved in the following way:

• let the user define a list of dependency names together with a variable that refers to a semantic version (e.g., docker:${DOCKER_VERSION} with DOCKER_VERSION equalling 18.09.0)
• the repository name is automatically derived as in #4 or specified by the user (separate parameters might be necessary, defaulting to ${CHOSEN_PARAMETER_NAME} that is fetched from envload)
• an algorithm creates all possible tuples of dependency names with or without the semantic version and with or without the minor and patch version numbers
• optional prefix and suffix parameters are added to all tags

As explained in #5