Kwalitee Issues

has_readme

Add a README to the distribution. It should contain a quick description of your module and how to install it.

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.

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: PDF-ReportWriter-1.5/lib/PDF/ReportWriter/Datasource.pm -- Around line 201: =over should be: '=over' or '=over positive_number' PDF-ReportWriter-1.5/lib/PDF/ReportWriter/Report.pm -- Around line 464: =over should be: '=over' or '=over positive_number' Around line 486: =over should be: '=over' or '=over positive_number' PDF-ReportWriter-1.5/lib/PDF/ReportWriter.pm -- Around line 2792: You forgot a '=back' before '=head3' Around line 2830: =back without =over Around line 2838: You forgot a '=back' before '=head3' Around line 3068: You forgot a '=back' before '=head2' You forgot a '=back' before '=head2' Around line 3083: =back without =over Around line 3085: =back without =over Around line 3444: =back without =over

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.

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: PDF::ReportWriter, PDF::ReportWriter::Datasource, PDF::ReportWriter::Datasource::DBI, PDF::ReportWriter::Report

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.0,1.00,1.5

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
PDF::ReportWriter 1.5 metacpan
PDF::ReportWriter::Datasource 1.00 metacpan
PDF::ReportWriter::Datasource::DBI 1.0 metacpan
PDF::ReportWriter::Report 1.0 metacpan

Other Files

Changes metacpan
MANIFEST metacpan
META.yml metacpan
Makefile.PL metacpan