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.
No Core Issues.
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
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: Apache::Session, Apache::Session::DB_File, Apache::Session::File, Apache::Session::Flex, Apache::Session::Generate::MD5, Apache::Session::Generate::ModUniqueId, Apache::Session::Generate::ModUsertrack, Apache::Session::Informix, Apache::Session::Lock::File, Apache::Session::Lock::MySQL, Apache::Session::Lock::Null, Apache::Session::Lock::Semaphore, Apache::Session::Lock::Sybase, Apache::Session::MySQL, Apache::Session::Oracle, Apache::Session::Postgres, Apache::Session::Serialize::Base64, Apache::Session::Serialize::Storable, Apache::Session::Serialize::Sybase, Apache::Session::Serialize::UUEncode, Apache::Session::Store::DBI, Apache::Session::Store::DB_File, Apache::Session::Store::File, Apache::Session::Store::Informix, Apache::Session::Store::MySQL, Apache::Session::Store::Oracle, Apache::Session::Store::Postgres, Apache::Session::Store::Sybase, Apache::Session::Sybase
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Error: 0.02,1.00,1.01,1.02,1.03,1.04,1.54,1.88,2.12
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.
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.
| Name | Abstract | Version | View |
|---|---|---|---|
| Apache::Session | A persistence framework for session data | 1.88 | metacpan |
| Apache::Session::DB_File | An implementation of Apache::Session | 1.01 | metacpan |
| Apache::Session::File | An implementation of Apache::Session | 1.54 | metacpan |
| Apache::Session::Flex | Specify everything at runtime | 1.01 | metacpan |
| Apache::Session::Generate::MD5 | Use MD5 to create random object IDs | 2.12 | metacpan |
| Apache::Session::Generate::ModUniqueId | mod_unique_id for session ID generation | 0.02 | metacpan |
| Apache::Session::Generate::ModUsertrack | mod_usertrack for session ID generation | 0.02 | metacpan |
| Apache::Session::Informix | An implementation of Apache::Session | 1.01 | metacpan |
| Apache::Session::Lock::File | Provides mutual exclusion using flock | 1.04 | metacpan |
| Apache::Session::Lock::MySQL | Provides mutual exclusion using MySQL | 1.01 | metacpan |
| Apache::Session::Lock::Null | Does not actually provides mutual exclusion | 1.01 | metacpan |
| Apache::Session::Lock::Semaphore | Provides mutual exclusion through semaphores | 1.04 | metacpan |
| Apache::Session::Lock::Sybase | Provides mutual exclusion using Sybase | 1.00 | metacpan |
| Apache::Session::MySQL | An implementation of Apache::Session | 1.01 | metacpan |
| Apache::Session::Oracle | An implementation of Apache::Session | 1.01 | metacpan |
| Apache::Session::Postgres | An implementation of Apache::Session | 1.01 | metacpan |
| Apache::Session::Serialize::Base64 | Use Storable and MIME::Base64 to zip up persistent data | 1.01 | metacpan |
| Apache::Session::Serialize::Storable | Use Storable to zip up persistent data | 1.01 | metacpan |
| Apache::Session::Serialize::Sybase | Use Storable to zip up persistent data and unpack/pack to put into Sybase-compatible image field | 1.00 | metacpan |
| Apache::Session::Serialize::UUEncode | Use Storable and C<pack()> to zip up persistent data | 1.01 | metacpan |
| Apache::Session::Store::DBI | 1.02 | metacpan | |
| Apache::Session::Store::DB_File | Use DB_File to store persistent objects | 1.01 | metacpan |
| Apache::Session::Store::File | Store persistent data on the filesystem | 1.03 | metacpan |
| Apache::Session::Store::Informix | Store persistent data in a Informix database | 1.01 | metacpan |
| Apache::Session::Store::MySQL | Store persistent data in a MySQL database | 1.04 | metacpan |
| Apache::Session::Store::Oracle | Store persistent data in a Oracle database | 1.01 | metacpan |
| Apache::Session::Store::Postgres | Store persistent data in a Postgres database | 1.03 | metacpan |
| Apache::Session::Store::Sybase | Store persistent data in a Sybase database | 1.01 | metacpan |
| Apache::Session::Sybase | An implementation of Apache::Session | 1.00 | metacpan |