CPANTS

PodParser 1.27 Deleted

Kwalitee Issues

This is not the latest release. The following issues may have already been fixed in the newer releases.

Take a look at the META.yml Spec at https://metacpan.org/pod/CPAN::Meta::History::Meta_1_4 (for version 1.4) or https://metacpan.org/pod/CPAN::Meta::Spec (for version 2), and change your META.yml accordingly.

Error: Expected a map structure from string or file. (requires) [Validation: 1.0]

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.

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: Pod::ParseUtils

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: PodParser-1.27/lib/Pod/InputObjects.pm -- Around line 41: You can't have =items (as at line 54) unless the first thing after the =over is an =item

6 Extra Issues

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: Pod::Checker, Pod::Find, Pod::InputObjects, Pod::ParseUtils, Pod::Parser, Pod::PlainText, Pod::Select, Pod::Usage

consistent_version

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

Error: 0.24,0.31,1.13,1.14,1.16,1.42,2.02

3 Experimental Issues

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
Pod::Checker		1.42	metacpan
Pod::Find	find POD documents in directory trees	0.24	metacpan
Pod::InputObjects	objects representing POD input paragraphs, commands, etc.	1.14	metacpan
Pod::ParseUtils	helpers for POD parsing and conversion	0.31	metacpan
Pod::Parser	base class for creating POD filters and translators	1.14	metacpan
Pod::PlainText	Convert POD data to formatted ASCII text	2.02	metacpan
Pod::Select		1.13	metacpan
Pod::Usage		1.16	metacpan

Provides

Name	File	View
Pod::Cache	lib/Pod/ParseUtils.pm	metacpan
Pod::Cache::Item	lib/Pod/ParseUtils.pm	metacpan
Pod::Hyperlink	lib/Pod/ParseUtils.pm	metacpan
Pod::InputSource	lib/Pod/InputObjects.pm	metacpan
Pod::InteriorSequence	lib/Pod/InputObjects.pm	metacpan
Pod::List	lib/Pod/ParseUtils.pm	metacpan
Pod::Paragraph	lib/Pod/InputObjects.pm	metacpan
Pod::ParseTree	lib/Pod/InputObjects.pm	metacpan

Other Files


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