Kwalitee Issues

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.

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: AFS, AFS::ACL, AFS::BOS, AFS::CM, AFS::Cell, AFS::FS, AFS::KAS, AFS::KTC_EKEY, AFS::KTC_PRINCIPAL, AFS::KTC_TOKEN, AFS::PTS, AFS::Utils, AFS::VLDB, AFS::VOS

no_pod_errors

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

Error: AFS-2.4.1/pod/v1/afsperlka.pod -- Around line 61: Non-ASCII character seen before =encoding in 'userentered'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperl.pod -- Around line 256: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlacl.pod -- Around line 301: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlbase.pod -- Around line 136: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlbos.pod -- Around line 463: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlcell.pod -- Around line 135: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlcm.pod -- Around line 185: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlfs.pod -- Around line 147: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlkas.pod -- Around line 270: Non-ASCII character seen before =encoding in 'ticketgranting'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlktck.pod -- Around line 145: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlktcp.pod -- Around line 190: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlktct.pod -- Around line 303: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlpts.pod -- Around line 401: Non-ASCII character seen before =encoding in 'nonzero'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlutils.pod -- Around line 116: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlvldb.pod -- Around line 319: Non-ASCII character seen before =encoding in '©'. Assuming CP1252 AFS-2.4.1/pod/v2/afsperlvos.pod -- Around line 369: Non-ASCII character seen before =encoding in '©'. Assuming CP1252

has_meta_json

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

proper_libs

Move your *.pm files in a directory named 'lib'. The directory structure should look like 'lib/Your/Module.pm' for a module named 'Your::Module'. If you need to provide additional files, e.g. for testing, that should not be considered for Kwalitee, then you should look at the 'provides' map in META.yml to limit the files scanned; or use the 'no_index' map to exclude parts of the distribution.

Error: src/AFS.pm, src/ACL/ACL.pm, src/BOS/BOS.pm, src/CM/CM.pm, src/Cell/Cell.pm, src/FS/FS.pm, src/KAS/KAS.pm, src/KTC_EKEY/KTC_EKEY.pm, src/KTC_PRINCIPAL/KTC_PRINCIPAL.pm, src/KTC_TOKEN/KTC_TOKEN.pm, src/PTS/PTS.pm, src/Utils/Utils.pm, src/VLDB/VLDB.pm, src/VOS/VOS.pm

use_warnings

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: AFS, AFS::ACL, AFS::BOS, AFS::CM, AFS::Cell, AFS::FS, AFS::KAS, AFS::KTC_EKEY, AFS::KTC_PRINCIPAL, AFS::KTC_TOKEN, AFS::PTS, AFS::Utils, AFS::VLDB, AFS::VOS

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
AFS 2.004001 metacpan
AFS::ACL 2.004001 metacpan
AFS::BOS 2.004001 metacpan
AFS::CM 2.004001 metacpan
AFS::Cell 2.004001 metacpan
AFS::FS 2.004001 metacpan
AFS::KAS 2.004001 metacpan
AFS::KTC_EKEY 2.004001 metacpan
AFS::KTC_PRINCIPAL 2.004001 metacpan
AFS::KTC_TOKEN 2.004001 metacpan
AFS::PTS 2.004001 metacpan
AFS::Utils 2.004001 metacpan
AFS::VLDB 2.004001 metacpan
AFS::VOS 2.004001 metacpan

Other Files

MANIFEST metacpan
META.yml metacpan
Makefile.PL metacpan
README metacpan
src/ACL/Makefile.PL metacpan
src/BOS/Makefile.PL metacpan
src/CM/Makefile.PL metacpan
src/Cell/Makefile.PL metacpan
src/FS/Makefile.PL metacpan
src/KAS/Makefile.PL metacpan
src/KTC_EKEY/Makefile.PL metacpan
src/KTC_PRINCIPAL/Makefile.PL metacpan
src/KTC_TOKEN/Makefile.PL metacpan
src/Makefile.PL metacpan
src/PTS/Makefile.PL metacpan
src/Utils/Makefile.PL metacpan
src/VLDB/Makefile.PL metacpan
src/VOS/Makefile.PL metacpan