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.
| Author/Maintainer | AFLOTT |
|---|---|
| Version | |
| Release Date | 2011-09-29 |
| Kwalitee | 116.67 |
| Core Kwalitee | 93.33 |
| External Links |
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 report us if they are false.
| metric | remedy |
|---|---|
| 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' 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 |
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. |
| use warnings |
This distribution does not 'use warnings;' 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' 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. |