Most probably CPANTS databases are being regenerated from scratch due to major changes in Kwalitee metrics or updates of relevant modules/perl. Usually this maintenance takes about a day or two, and some of the information may be old or missing tentatively. Sorry for the inconvenience.
If you use Mac OS X >= 10.6, use gnu tar (/usr/bin/gnutar) to avoid PAX headers. It's also important to rename (shorten) long file names (>= 100 characters) in the distribution.
Error: PaxHeader/CLI-0.24,PaxHeader/CLI-0.24,CLI-0.24/PaxHeader/Changes,CLI-0.24/PaxHeader/Changes,CLI-0.24/PaxHeader/CLI,CLI-0.24/PaxHeader/CLI,CLI-0.24/PaxHeader/CLI.pm,CLI-0.24/PaxHeader/CLI.pm,CLI-0.24/PaxHeader/interactive.pl,CLI-0.24/PaxHeader/interactive.pl,CLI-0.24/PaxHeader/Makefile.PL,CLI-0.24/PaxHeader/Makefile.PL,CLI-0.24/PaxHeader/META.json,CLI-0.24/PaxHeader/META.json,CLI-0.24/PaxHeader/META.yml,CLI-0.24/PaxHeader/META.yml,CLI-0.24/PaxHeader/README,CLI-0.24/PaxHeader/README,CLI-0.24/PaxHeader/t.pl,CLI-0.24/PaxHeader/t.pl,CLI-0.24/PaxHeader/test.config,CLI-0.24/PaxHeader/test.config,CLI-0.24/PaxHeader/test.pl,CLI-0.24/PaxHeader/test.pl,CLI-0.24/CLI/PaxHeader/Array.pm,CLI-0.24/CLI/PaxHeader/Array.pm,CLI-0.24/CLI/PaxHeader/Base.pm,CLI-0.24/CLI/PaxHeader/Base.pm,CLI-0.24/CLI/PaxHeader/Command.pm,CLI-0.24/CLI/PaxHeader/Command.pm,CLI-0.24/CLI/PaxHeader/Hash.pm,CLI-0.24/CLI/PaxHeader/Hash.pm,CLI-0.24/CLI/PaxHeader/MixedArray.pm,CLI-0.24/CLI/PaxHeader/MixedArray.pm,CLI-0.24/CLI/PaxHeader/Var.pm,CLI-0.24/CLI/PaxHeader/Var.pm
Add a MANIFEST to the distribution. Your buildtool should be able to autogenerate it (eg "make manifest" or "./Build manifest")
Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
Add =head1 LICENSE and the text of the license to the main module in your code.
Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually.
Error: Cannot find MANIFEST in dist.
Provide a short description in the NAME section of the pod (after the module name followed by a hyphen) at least for the main module of this distribution.
Make sure that the main module name and version are the same of the distribution.
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.
Add tests or move tests.pl to the t/ directory!
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.
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: CLI, CLI::Array, CLI::Base, CLI::Command, CLI::Hash, CLI::MixedArray, CLI::Var
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).
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.