Kwalitee Issues

meta_yml_conforms_to_known_spec

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: License 'Artistic' is invalid (license) [Validation: 1.3]

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.

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 Sun 23 Nov 2008 02:57:12 PM JST gpg: using DSA key 31F9562596406EA0 gpg: Can't check signature: No public key --- SIGNATURE Sun Nov 23 14:57:12 2008 +++ @@ -1,7 +1,7 @@ SHA1 7dfab147f3d0fac140c58043c4585e745f4b8fdf Changes SHA1 75787f12fb3b38fce5f388f80312900d9c4f660a MANIFEST SHA1 7e740186be7996b6ce3ed345d17f9760678a5c6b MANIFEST.SKIP -SHA1 584053e61753e83dcc78d9f6607f643e769f8919 META.yml +SHA1 ef4800a93b1da7b784633f04f3fed5071ab906fa META.yml SHA1 ed58aa4673275e4359323e8f687d3230143cd5b5 Makefile.PL SHA1 7e2cfa1b9efe0d502ee57717649c90ba4bd28ba9 inc/Module/Install.pm SHA1 6e1392d80a0f239eecd5664f7f21f922cedb9329 inc/Module/Install/Base.pm ==> 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.

Modules

Name Abstract Version View
String::BufferStack Nested buffers for templating systems 1.01 metacpan

Other Files

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