Kwalitee Issues

has_readme

Add a README to the distribution. It should contain a quick description of your module and how to install it.

has_manifest

Add a MANIFEST to the distribution. Your buildtool should be able to autogenerate it (eg "make manifest" or "./Build manifest")

has_meta_yml

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

has_buildtool

Add a Makefile.PL (for ExtUtils::MakeMaker/Module::Install) or a Build.PL (for Module::Build and its friends), or use a distribution builder such as Dist::Zilla, Dist::Milla, Minilla.

has_changelog

Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.

has_tests

Add tests!

has_version

Add a version number to the packed distribution. Or use a buildtool ('make dist' or 'Build dist')

has_proper_version

Remove all letters from the version number. If you want to mark a release as a developer release, use the scheme 'Module-1.00_01'

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.

manifest_matches_dist

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.

Error: Cannot find MANIFEST in dist.

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.

prereq_matches_use

List all used modules in META.yml requires

Error:

  • Data::Stack
  • Moose
  • Moose::Role

main_module_version_matches_dist_version

Make sure that the main module name and version are the same of the distribution.

has_meta_json

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

has_tests_in_t_dir

Add tests or move tests.pl to the t/ directory!

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: cmo/rpn/deco/CalcDeco.pm, cmo/rpn/deco/CalcImpl.pm, cmo/rpn/deco/Multiply.pm, cmo/rpn/deco/ICalc.pm, cmo/rpn/deco/Minus.pm, cmo/rpn/deco/Mod.pm, cmo/rpn/deco/Divide.pm, cmo/rpn/deco/MyStack.pm, cmo/rpn/deco/Plus.pm, cmo/rpn/deco/Sqrt.pm, cmo/rpn/deco/Token.pm

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.

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.

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
cmo::rpn::deco::CalcDeco metacpan
cmo::rpn::deco::CalcImpl metacpan
cmo::rpn::deco::Divide metacpan
cmo::rpn::deco::ICalc metacpan
cmo::rpn::deco::Minus metacpan
cmo::rpn::deco::Mod metacpan
cmo::rpn::deco::Multiply metacpan
cmo::rpn::deco::MyStack metacpan
cmo::rpn::deco::Plus metacpan
cmo::rpn::deco::Sqrt metacpan
cmo::rpn::deco::Token metacpan