Kwalitee Issues

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: Benchmark-Harness-1.10/Harness/Trace.pm -- Around line 87: Unknown directive: =item1 Around line 91: Unknown directive: =item1 Around line 101: Unknown directive: =item1 Around line 149: Unknown directive: =item1 Benchmark-Harness-1.10/Harness/TraceHighRes.pm -- Around line 139: Unknown directive: =item1 Around line 143: Unknown directive: =item1 Benchmark-Harness-1.10/Harness/ValuesHighRes.pm -- Around line 28: Unknown directive: =item1 Around line 32: Unknown directive: =item1 Benchmark-Harness-1.10/Harness.pm -- Around line 84: Unknown directive: =item2 Around line 89: Unknown directive: =item2 Around line 95: Unknown directive: =item2

meta_yml_declares_perl_version

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.

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.

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: Benchmark::Harness, Benchmark::Harness::Constants, Benchmark::Harness::Handler, Benchmark::Harness::Trace, Benchmark::Harness::TraceHighRes, Benchmark::Harness::Values, Benchmark::Harness::ValuesHighRes

meta_yml_has_provides

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.

meta_yml_has_repository_resource

Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).

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
Benchmark::Harness metacpan
Benchmark::Harness::Constants metacpan
Benchmark::Harness::Handler metacpan
Benchmark::Harness::Trace metacpan
Benchmark::Harness::TraceHighRes metacpan
Benchmark::Harness::Values metacpan
Benchmark::Harness::ValuesHighRes metacpan

Provides

Name File View
Benchmark::Harness::Handler::Trace Harness/Trace.pm metacpan
Benchmark::Harness::Handler::TraceHighRes Harness/TraceHighRes.pm metacpan
Benchmark::Harness::Handler::Values Harness/Values.pm metacpan
Benchmark::Harness::Handler::ValuesHighRes Harness/ValuesHighRes.pm metacpan

Other Files

MANIFEST metacpan
META.yml metacpan
Makefile.PL metacpan
README metacpan