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.
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
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 is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
|Test::Chimps||Collaborative Heterogeneous Infinite Monkey Perfectionification Service||0.07_01||metacpan|
|Test::Chimps::Report||Encapsulate a smoke test report||metacpan|
|Test::Chimps::ReportCollection||Encapsulate a collection of smoke test reports||metacpan|
|Test::Chimps::Server||Accept smoke report uploads and display smoke reports||metacpan|
|Test::Chimps::Server::Lister||Format the list of smoke reports||metacpan|