Kwalitee Issues

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.

main_module_version_matches_dist_version

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

valid_signature

Sign the dist as the last step before creating the archive. Take care not to modify/regenerate dist meta files or the manifest.

Error: Old SIGNATURE detected. Please inform the module author to regenerate SIGNATURE using Module::Signature version 0.82 or newer. gpg: Signature made Mon 13 Jul 2009 08:24:25 AM JST gpg: using DSA key 122F5DF7108E4046 gpg: Can't check signature: No public key --- SIGNATURE Mon Jul 13 08:24:32 2009 +++ @@ -1,7 +1,7 @@ SHA1 ad78bcb700873cfd6a6f4e93d400cf5e850a0ae3 Changes SHA1 1f52c6c033cb2412e047c7e2d9200aa03eba5793 MANIFEST SHA1 e476d8bd724d46eb9e255cc8afc98b92269e2255 MANIFEST.SKIP -SHA1 53b1a4dbaad37ced718e06700edc05e019d0956e META.yml +SHA1 0d53abd37e4d8f63fbd68efe7bf3d4b08489164c META.yml SHA1 074b7975f68941d5a32782e7f3dbffada190caec Makefile.PL SHA1 d69e7f71c0e6cc89349bded9d470222294a0d2e2 README SHA1 41afe2c04bb573b40e283e2b210ed70a47a3f8ba t/0-signature.t ==> MISMATCHED content between SIGNATURE and distribution files! <==

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.

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.

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.

Other Files

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