Most probably the CPANTS databases are being regenerated from scratch behind the scenes due to the major change in Kwalitee metrics or the update of relevant modules/perl. Usually this maintenance takes about a day or two, and some of the information may be old or missing tentatively. Sorry for the inconvenience.
These fails do affect your Kwalitee scores. This distribution may not be installed cleanly, or may have some issues in license or documentation. Please consider fixing them, or tell us if they are false.
| metric | remedy |
|---|---|
| metayml is parsable |
The META.yml file of this distribution could not be parsed by the version of CPAN::Meta::YAML.pm CPANTS is using. If you don't have one, add a META.yml file. Else, upgrade your YAML generator so it produces valid YAML. |
| metayml conforms to known spec |
META.yml does not conform to any recognised META.yml Spec. Take a look at the META.yml Spec at http://module-build.sourceforge.net/META-spec-v1.4.html (for version 1.4) or http://search.cpan.org/perldoc?CPAN::Meta::Spec (for version 2), and change your META.yml accordingly. |
| has meta yml |
The file "META.yml" is missing from this distribution. META.yml is needed by people maintaining module collections (like CPAN), for people writing installation tools, or just people who want to know some stuff about a distribution before downloading it. Add a META.yml to the distribution. Your buildtool should be able to autogenerate it. |
| 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. |
| use strict |
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. |
| no pod errors |
The documentation for this distribution contains syntactic errors in its POD. Note that this metric tests all .pl, .pm and .pod files, even if they are in t/. See 'pod_message' in the dist error view for more info. Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite. |
| consistent version |
This distribution has .pm files with inconsistent versions. Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade). |
These fails affect your total Kwalitee score, but don't affect the one for the Game. Some of them should be fixed by all means. Others are just matters of taste.
| metric | remedy |
|---|---|
| metayml declares perl version |
This distribution does not declare the minimum perl version in META.yml. If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs. |
| metayml has license |
This distribution does not have a license defined in META.yml. Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31. |
| 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. |
| use warnings |
This distribution does not 'use warnings;' (or its equivalents) in all of its modules. Note that this is not about that your modules actually warn when something bad happens. It's bad if nobody can tell if a module warns or not, without reading the source code of your favorite module that actually enforces warnings. In other words, it's bad if someone feels the need to add 'use warnings' to your modules. Add 'use warnings' (or its equivalents) to all modules (this will require perl > 5.6), or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens. |
| is prereq |
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.
| metric | remedy |
|---|---|
| metayml 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 does this automatically for you. |
| has separate license file |
This distribution does not have a LICENSE or LICENCE file in its root directory. This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later. |
| easily repackageable by fedora |
It is easy to repackage this module by Fedora. Fix each one of the metrics this depends on. |
| fits fedora license |
Fits the licensing requirements of Fedora (Acceptable licenses: (perl, apache, artistic_2, gpl, lgpl, mit, mozilla)). Replace the license or convince Fedora to accept this license as well. |