This distribution doesn't create a directory and extracts its content into this directory. Instead, it creates more than one directories (some of which are probably system-specific hidden files/directories), or it spews its content into the current directory, making it really hard/annoying to remove the unpacked package.
Pack the distribution with a proper command such as "make dist" and "./Build dist", or use a distribution builder such as Dist::Zilla, Dist::Milla, Minilla.
The file "README" is missing from this distribution. The README provides some basic information to users prior to downloading and unpacking the distribution.
Add a README to the distribution. It should contain a quick description of your module and how to install it.
|no broken module install||
This distribution uses an obsolete version of Module::Install. Versions of Module::Install prior to 0.61 might not work on some systems at all. Additionally if your Makefile.PL uses the 'auto_install()' feature, you need at least version 0.64. Also, 1.04 is known to be broken.
Upgrade the bundled version of Module::Install to the most current release. Alternatively, you can switch to another build system / installer that does not suffer from this problem. (ExtUtils::MakeMaker, Module::Build both of which have their own set of problems.)
|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.
|package version matches dist version||
None of the package versions in this distribution matches the distribution version.
Fix the version(s).
|metayml declares perl version||
This distribution does not declare the minimum perl version in META.yml.
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.
|metayml has provides||
This distribution does not have a list of provided modules defined in META.yml.
|has separate license file||
This distribution does not have a LICENSE or LICENCE file in its root directory.