Kwalitee Issues

has_manifest

Add a MANIFEST to the distribution. Your buildtool should be able to autogenerate it (eg "make manifest" or "./Build manifest")

has_meta_yml

Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.

has_tests

Add tests!

has_human_readable_license

Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.

has_license_in_source_file

Add =head1 LICENSE and the text of the license to the main module in your code.

manifest_matches_dist

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.

has_abstract_in_pod

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.

use_strict

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.

Error: Schedule::Chronic, Schedule::Chronic::Base, Schedule::Chronic::Constraint::DiskIO, Schedule::Chronic::Constraint::Freq, Schedule::Chronic::Constraint::Inactivity, Schedule::Chronic::Constraint::Loadavg, Schedule::Chronic::Tab, Schedule::Chronic::Timer

main_module_version_matches_dist_version

Make sure that the main module name and version are the same of the distribution.

no_pod_errors

Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.

Error: Chronic-0.02/docs/chronicd.pod -- Around line 123: You forgot a '=back' before '=head1' Around line 131: =back without =over

has_meta_json

Add a META.json to the distribution. Your buildtool should be able to autogenerate it.

has_tests_in_t_dir

Add tests or move tests.pl to the t/ directory!

meta_yml_has_license

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.

has_known_license_in_source_file

Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.

use_warnings

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: Schedule::Chronic, Schedule::Chronic::Base, Schedule::Chronic::Constraint::DiskIO, Schedule::Chronic::Constraint::Freq, Schedule::Chronic::Constraint::Inactivity, Schedule::Chronic::Constraint::Loadavg, Schedule::Chronic::Tab, Schedule::Chronic::Timer

has_separate_license_file

This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.

Modules

Name Abstract Version View
Schedule::Chronic metacpan
Schedule::Chronic::Base metacpan
Schedule::Chronic::Constraint::DiskIO metacpan
Schedule::Chronic::Constraint::Freq metacpan
Schedule::Chronic::Constraint::Inactivity metacpan
Schedule::Chronic::Constraint::Loadavg metacpan
Schedule::Chronic::Tab metacpan
Schedule::Chronic::Timer metacpan

Other Files

Makefile.PL metacpan
README metacpan