Kwalitee Issues

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.

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.12/Harness/Trace.pm -- Around line 118: Unknown directive: =item1Around line 122: Unknown directive: =item1Around line 132: Unknown directive: =item1Around line 180: Unknown directive: =item1 Benchmark-Harness-1.12/Harness/TraceHighRes.pm -- Around line 139: Unknown directive: =item1Around line 143: Unknown directive: =item1 Benchmark-Harness-1.12/Harness/ValuesHighRes.pm -- Around line 28: Unknown directive: =item1Around line 32: Unknown directive: =item1 Benchmark-Harness-1.12/Harness.pm -- Around line 72: Unknown directive: =item2Around line 77: Unknown directive: =item2Around line 83: Unknown directive: =item2

package_version_matches_dist_version

Fix the version(s).

consistent_version

Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).

Error: 1.01,1.02,1.11

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_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.

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 (this will require perl > 5.6), 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

has_separate_license_file

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

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).

Modules

Name Abstract Version View
Benchmark::Harness 1.11 metacpan
Benchmark::Harness::Constants metacpan
Benchmark::Harness::Handler 1.01 metacpan
Benchmark::Harness::Trace 1.02 metacpan
Benchmark::Harness::TraceHighRes 1.01 metacpan
Benchmark::Harness::Values 1.01 metacpan
Benchmark::Harness::ValuesHighRes 1.01 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