Language-Tea

The build tool (Build.PL/Makefile.PL) is executable. This is bad because you should specify which perl you want to use while installing.

Change the permissions of Build.PL/Makefile.PL to not-executable.

This distribution has at least one file with non-portable characters in its filename, which may cause problems under some environments.

Rename those files with alphanumerical characters, or maybe remove them because in many cases they are automatically generated for local installation.

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 the 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.

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.

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.

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.

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 modules 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 the 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.

This distribution is not required by another distribution by another author.

Convince / force / bribe another CPAN author to use this distribution.

This distribution uses a module or a dist in it's test suite that's not listed as a build prerequisite.

List all modules used in the test suite in META.yml build_requires

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.

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.

It is easy to repackage this module by Fedora.

Fix each one of the metrics this depends on.

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.