|has meta yml||
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
|has proper version||
The version number isn't a number. It probably contains letter besides a leading 'v', which it shouldn't
Remove all letters from the version number. If you want to mark a release as a developer release, use the scheme 'Module-1.00_01'
This distribution does not 'use strict;' (or its equivalents) in all of its modules. Note that this is not about the actual strictness of the modules. It's bad if nobody can tell whether the modules are strictly written or not, without reading the source code of your favorite clever module that actually enforces strictness. In other words, it's bad if someone feels the need to add 'use strict' to your modules.
Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.
|prereq matches use||
This distribution uses a module or a dist that's not listed as a prerequisite.
List all used modules in META.yml requires
|package version matches dist version||
None of the package versions in this distribution matches the distribution version.
Fix the version(s).
|meta yml has license||
This distribution does not have a license defined in META.yml.
|has known license in source file||
Does not have license information in any of its source files, or the information is not recognized by Software::License
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
These fails are not serious and don't affect your Kwalitee scores at all.
|has separate license file||
This distribution does not have a LICENSE or LICENCE file in its root directory.