Kwalitee Issues


Take a look at the META.yml Spec at (for version 1.4) or (for version 2), and change your META.yml accordingly.

Error: Expected a list structure (author) [Validation: 1.3];License '<undef>' is invalid (license) [Validation: 1.3];Missing mandatory field, 'abstract' (abstract) [Validation: 1.3];Missing mandatory field, 'author' (author) [Validation: 1.3];Missing mandatory field, 'license' (license) [Validation: 1.3];value is an undefined string (abstract) [Validation: 1.3]


Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.


Add =head1 LICENSE and the text of the license to the main module in your code.


Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.

Error: WordPress-API-1.10/lib/WordPress/Base/Data/ -- Around line 49: Unknown directive: =haed1 WordPress-API-1.10/lib/WordPress/Base/Data/ -- Around line 68: Unknown directive: =haed1 WordPress-API-1.10/lib/WordPress/Base/Data/ -- Around line 25: Unknown directive: =haed1 WordPress-API-1.10/lib/WordPress/Base/Data/ -- Around line 34: Unknown directive: =haed1


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.


Add a META.json to the distribution. Your buildtool should be able to autogenerate it.


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.


Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.


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: WordPress::API, WordPress::API::Category, WordPress::API::MediaObject, WordPress::API::Page, WordPress::API::Post, WordPress::Base::Content, WordPress::Base::Data::Author, WordPress::Base::Data::Category, WordPress::Base::Data::MediaObject, WordPress::Base::Data::Object, WordPress::Base::Data::Page, WordPress::Base::Data::Post, WordPress::Base::Date, WordPress::Base::Object


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

Error: 1.02,1.04,1.05,1.10


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.


Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).


This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.


Name Abstract Version View
WordPress::API 1.10 metacpan
WordPress::API::Category metacpan
WordPress::API::MediaObject metacpan
WordPress::API::Page metacpan
WordPress::API::Post metacpan
WordPress::Base::Content 1.02 metacpan
WordPress::Base::Data::Author metacpan
WordPress::Base::Data::Category metacpan
WordPress::Base::Data::MediaObject metacpan
WordPress::Base::Data::Object 1.05 metacpan
WordPress::Base::Data::Page metacpan
WordPress::Base::Data::Post metacpan
WordPress::Base::Date 1.04 metacpan
WordPress::Base::Object metacpan
WordPress::Base::Text text helpers metacpan

Other Files

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