Pinwheel

The distribution hasn't got a Changelog (named something like m/^chang(es?|log)|history$/i. A Changelog helps people decide if they want to upgrade to a new version.

Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.

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.

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.

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.

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 uses a module or a dist that's not listed as a prerequisite.

List all used modules in META.yml requires

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

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

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

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.