Kwalitee Issues

has_proper_version

Remove all letters from the version number. If you want to mark a release as a developer release, use the scheme 'Module-1.00_01'

main_module_version_matches_dist_version

Make sure that the main module name and version are the same of the distribution.

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_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: Config::Neat, Config::Neat::Array, Config::Neat::Inheritable, Config::Neat::Render, Config::Neat::Schema, Config::Neat::Util

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
Config::Neat Parse/render human-readable configuration files with inheritance and schema validation 1.3 metacpan
Config::Neat::Array Class for array-like config nodes 1.3 metacpan
Config::Neat::Inheritable Config::Neat files with inheritance 1.3 metacpan
Config::Neat::Render Render configs in Config::Neat format 1.3 metacpan
Config::Neat::Schema Validate Config::Neat files against schema 1.3 metacpan
Config::Neat::Util Common utility functions for other Config::Neat modules 1.3 metacpan

Other Files

Build.PL metacpan
Changes metacpan
MANIFEST metacpan
META.json metacpan
META.yml metacpan
Makefile.PL metacpan
README metacpan