Improving ccsh check behaviour

[Nereboss]

Question

Preparation

Please check these resources first before posting a question

• I searched for answers in older issues
• I looked into the README.md
• I read the website

Question

Should we improve the behaviour of ccsh check?
I find it to be not the most intuitive right now:

• When the input is a valid file, it simply runs and exits without any additional information. This can leave the user guessing if it even ran correctly as there is no feedback
• When the input is an invalid file, it prints an exception containing what was wrong. At first sight this looks like the program ran into an error and not, that it successfully ran and concluded that the file is invalid.

How often is this functionality used? Would it be worth it to improve its output to more clearly state its findings?

[ChristianHuehn]

I can say that in the last two audits I attended, there werent any usages of ccsh check. I will ask around 👍 thanks