|has human readable license||
This distribution does not have a license defined in the documentation or in a file called LICENSE
Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
|has license in source file||
Does not have license information in any of its source files
Add =head1 LICENSE and the text of the license to the main module in your code.
|manifest matches dist||
MANIFEST does not match the contents of this distribution.
Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually.
|has abstract in pod||
No abstract (short description of a module) is found in pod from this distribution.
Provide a short description in the NAME section of the pod (after the module name followed by a hyphen) at least for the main module of this distribution.
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.
|has tests in t dir||
This distribution contains either a file called 'test.pl' (the old test file) or is missing a directory called 't'. This indicates that it uses the old test mechanism or it has no test-suite.
Add tests or move tests.pl to the t/ directory!
There is more than one .pm file in the base dir, or the .pm files are not in lib/ directory.
Move your *.pm files in a directory named 'lib'. The directory structure should look like 'lib/Your/Module.pm' for a module named 'Your::Module'. If you need to provide additional files, e.g. for testing, that should not be considered for Kwalitee, then you should look at the 'provides' map in META.yml to limit the files scanned; or use the 'no_index' map to exclude parts of the distribution.
|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.
This distribution is not required by another distribution by another author.
Convince / force / bribe another CPAN author to use this distribution.
These fails are not serious and don't affect your Kwalitee scores at all.
|meta yml has provides||
This distribution does not have a list of provided modules defined in META.yml.
Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.
|meta yml has repository resource||
This distribution does not have a link to a repository in META.yml.
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
|has separate license file||
This distribution does not have a LICENSE or LICENCE file in its root directory.