Kwalitee Issues

no_pod_errors

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

Error: cPanel-PublicAPI-2/lib/cPanel/PublicAPI.pod -- Around line 130: Non-ASCII character seen before =encoding in '“Setup'. Assuming UTF-8

use_strict

Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.

Error: cPanel::PublicAPI::Utils, cPanel::PublicAPI::WHM, cPanel::PublicAPI::WHM::API, cPanel::PublicAPI::WHM::CachedVersion, cPanel::PublicAPI::WHM::DNS, cPanel::PublicAPI::WHM::JSONAPI, cPanel::PublicAPI::WHM::Legacy, cPanel::PublicAPI::WHM::XMLAPI

consistent_version

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

Error: 1,2

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

meta_yml_has_license

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.

use_warnings

Add 'use warnings' (or its equivalents) to all modules (this will require perl > 5.6), or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.

Error: cPanel::PublicAPI, cPanel::PublicAPI::Utils, cPanel::PublicAPI::WHM, cPanel::PublicAPI::WHM::API, cPanel::PublicAPI::WHM::CachedVersion, cPanel::PublicAPI::WHM::DNS, cPanel::PublicAPI::WHM::JSONAPI, cPanel::PublicAPI::WHM::Legacy, cPanel::PublicAPI::WHM::XMLAPI

has_separate_license_file

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

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

Modules

Name Abstract Version View
cPanel::PublicAPI A perl interface for interacting with cPanel 2 metacpan
cPanel::PublicAPI::Utils Provides some internally used utility functions for cPanel::PublicAPI, should never be used externally. metacpan
cPanel::PublicAPI::WHM Legacy interface for querying WHM. 1 metacpan
cPanel::PublicAPI::WHM::CachedVersion Allows for lookups of remote versions of cPanel & WHM. 1 metacpan

Provides

Name File View
cPanel::PublicAPI::API lib/cPanel/PublicAPI/WHM/API.pm metacpan
cPanel::PublicAPI::DNS lib/cPanel/PublicAPI/WHM/DNS.pm metacpan
cPanel::PublicAPI::JSONAPI lib/cPanel/PublicAPI/WHM/JSONAPI.pm metacpan
cPanel::PublicAPI::Legacy lib/cPanel/PublicAPI/WHM/Legacy.pm metacpan
cPanel::PublicAPI::XMLAPI lib/cPanel/PublicAPI/WHM/XMLAPI.pm metacpan

Other Files

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