|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.
|no mymeta files||
This distribution contains MYMETA.* files which should be used only locally. This metric should be integrated into 'no_generated_files' eventually, but as MYMETA.* files are recent inventions, you might need to take special care if MANIFEST.SKIP exists in your distribution. Hence this metric.
Update MANIFEST.SKIP to exclude MYMETA files. If you are lazy, add "#!install_default" in your MANIFEST.SKIP and update your ExtUtils::Manifest if necessary, then some of the most common files will be excluded.
|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.
|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.
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).
There is more than one .pm file in the base dir, or the .pm files are not in lib/ directory.
Move your *.pm files in a directory named 'lib'. The directory structure should look like 'lib/Your/Module.pm' for a module named 'Your::Module'.
|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.
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.
|no invalid versions||
This distribution has .pm files with an invalid version.
Fix the version numbers so that version::is_lax($version) returns true.
|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.