CPANTS

Parse-RecDescent-FAQ 3.0 Deleted

Kwalitee Issues

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

has_readme: Add a README to the distribution. It should contain a quick description of your module and how to install it.
has_meta_yml: Add a META.yml to the distribution. Your buildtool should be able to autogenerate 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.
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: EDIT_FAQ.tt.DO_NOT_EDIT_FAQ, Parse::RecDescent::FAQ
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: Parse-RecDescent-FAQ-3.0/FAQ.pm -- Around line 984: =over should be: '=over' or '=over positive_number' Around line 1463: =over should be: '=over' or '=over positive_number' Around line 1557: =back doesn't take any parameters, but you said =back =head2 More on blank lines Around line 1567: =over should be: '=over' or '=over positive_number' Around line 1632: =over should be: '=over' or '=over positive_number' Around line 2032: =over should be: '=over' or '=over positive_number' You can't have =items (as at line 2092) unless the first thing after the =over is an =item Around line 2145: Expected '=item *'

6 Extra Issues

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!
proper_libs: Move your *.pm files in a directory named 'lib'. The directory structure should look like 'lib/Your/Module.pm' for a module named 'Your::Module'. If you need to provide additional files, e.g. for testing, that should not be considered for Kwalitee, then you should look at the 'provides' map in META.yml to limit the files scanned; or use the 'no_index' map to exclude parts of the distribution.

Error: EDIT_FAQ.tt.DO_NOT_EDIT_FAQ.pm, FAQ.pm
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: EDIT_FAQ.tt.DO_NOT_EDIT_FAQ, Parse::RecDescent::FAQ

4 Experimental Issues

has_separate_license_file: This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
has_security_doc: Add SECURITY(.pod|md). See Software::Security::Policy.
security_doc_contains_contact: Add SECURITY(.pod|md) and add a contact address. See Software::Security::Policy.
has_contributing_doc: Add CONTRIBUTING(.pod|md). See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.

Modules

Name	Abstract	Version	View
Parse::RecDescent::FAQ	the official, authorized FAQ for Parse::RecDescent.	2.37	metacpan

Other Files


Changes	metacpan
MANIFEST	metacpan
Makefile.PL	metacpan