It would be nice if lynis would gather (and report in the portal/reports) information about user-accounts:

• Expired or soon to expire passwords (passwd -e)
• Locked accounts (passwd -S )
• Expired accounts (chage -E / chage -l )

Is your feature request related to a problem? Please describe.
User Resource lacks tags.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

There are some use case for me where certain tags are exempted from a compliance rule and others are not.
Due to lack of tags information being captured as part of IAM user resource, am unable to implem

There are at least two more security relevant headers that we should test for and produce judgements on:

• Cross-Origin-Opener-Policy
• Cross-Origin-Embedder-Policy

More resources:

• https://hacks.mozilla.org/2020/07/safely-reviving-shared-memory/
• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy
• https://developer.mozilla.org/en-US/docs/Web/HT

Now that we want to give more value to it, it would be nice if we could break down the areas of development on the project based on conventional commits.

Things we could have there

• Stats per scope
• Stats per action
• Stats per author
• Time range selector for the statistics