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.
Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.
Make sure that the main module name and version are the same of the distribution.
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
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).
| Name | Abstract | Version | View |
|---|---|---|---|
| Flower | passive agent | metacpan | |
| Flower::Chronos | metacpan | ||
| Flower::Chronos::Application::Base | metacpan | ||
| Flower::Chronos::Application::Chromium | metacpan | ||
| Flower::Chronos::Application::Firefox | metacpan | ||
| Flower::Chronos::Application::GnomeTerminal | metacpan | ||
| Flower::Chronos::Application::GoogleChrome | metacpan | ||
| Flower::Chronos::Application::Pidgin | metacpan | ||
| Flower::Chronos::Application::Skype | metacpan | ||
| Flower::Chronos::Application::Thunderbird | metacpan | ||
| Flower::Chronos::Logger | metacpan | ||
| Flower::Chronos::Logger::Base | metacpan | ||
| Flower::Chronos::Logger::Stdout | metacpan | ||
| Flower::Chronos::Report | metacpan | ||
| Flower::Chronos::Tracker | metacpan | ||
| Flower::Chronos::Utils | metacpan | ||
| Flower::Chronos::X11 | metacpan | ||
| Flower::File | metacpan | ||
| Flower::Files | metacpan | ||
| Flower::Interface | metacpan | ||
| Flower::Node | metacpan | ||
| Flower::Nodes | metacpan | ||
| Flower::Rest | metacpan | ||
| Flower::Upload | metacpan |