Introduction

This is a collection of the results gathered from various code analysis tools, which was implemented through 3rd party services or with Github actions in week 6-8.

Container-scan results:

A branch called 'code-analysis/#149Address_feedback_from_various_code_analysis_tools' from issue #149 was created which uses the Github Action Container-scan. A result from this can be seen here: [container-scan] minitwit-go-dev:latest and in terminal output style here.

Running golint results:

When running the command golint ./... 10 different 'errors' appear. These can be found here. They are mostly Go specific stylistic 'errors' and are not that important to fix.

Shellcheck results:

When running spellcheck in the /scripts folder, the results can be seen here, but are mostly about unused stmts, string handling and the error handling when using the cd cmd.

Code climate results:

A list of 14 issues can be found here, but are mostly issues about code duplication, "Cognitive Complexity" and lines of code in a file. So code smell and duplication.

Bettercodehub results:

Results can be found here, which can also be seen on the picture below.

SonarCloud Code Analysis results:

Results can be found here or here, which again is about code smells, one "bug" in some HTML file and some test hardcoded passwords, which does not matter. They have a concept of "quality gate", which does some gatekeeping for quality control, where the following thresholds should not be exceeded.