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.
Fix MANIFEST.SKIP or use an authoring tool which respects MANIFEST.SKIP. Note that each entry in MANIFEST.SKIP is a regular expression. You may need to add appropriate meta characters not to ignore necessary stuff.
Error: Makefile,blib/arch/.exists,blib/arch/auto/OptArgs/.exists,blib/arch/auto/OptArgs,blib/arch/auto,blib/arch,blib/bin/.exists,blib/bin,blib/lib/.exists,blib/lib/App/optargs.pm,blib/lib/App,blib/lib/OptArgs.pm,blib/lib/OptArgs.pod,blib/lib/auto/OptArgs/.exists,blib/lib/auto/OptArgs,blib/lib/auto,blib/lib,blib/man1/.exists,blib/man1/optargs.1,blib/man1,blib/man3/.exists,blib/man3/App::optargs.3,blib/man3/OptArgs.3,blib/man3,blib/script/.exists,blib/script/optargs,blib/script,blib,pm_to_blib
Remove the offending files/directories!
Error: Makefile, pm_to_blib
Rename those files with alphanumerical characters, or maybe remove them because in many cases they are automatically generated for local installation.
Error:
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.
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:
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 a META.json to the distribution. Your buildtool should be able to autogenerate it.
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'. If you need to provide additional files, e.g. for testing, that should not be considered for Kwalitee, then you should look at the 'provides' map in META.yml to limit the files scanned; or use the 'no_index' map to exclude parts of the distribution.
Error: blib/lib/App/optargs.pm, blib/lib/OptArgs.pm
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.
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
Add SECURITY(.pod|md). See Software::Security::Policy.
Add SECURITY(.pod|md) and add a contact address. See Software::Security::Policy.
Add CONTRIBUTING(.pod|md). See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.