Kwalitee Issues


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.


Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually.


  • MANIFEST (7) does not match dist (8):
  • Missing in MANIFEST: README


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

Error: REST-Google-Apps-EmailSettings-1.1.6/lib/REST/Google/Apps/EmailSettings.pod -- Around line 420: Non-ASCII character seen before =encoding in '›'. Assuming UTF-8


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


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


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.


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


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).


Name Abstract Version View
REST::Google::Apps::EmailSettings A Perl library to Google's RESTful Apps Email Settings API 1.001006 metacpan

Other Files

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