Kwalitee Issues

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_tests

Add tests!

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:

  • DBI
  • Date::Manip
  • Gtk
  • Gtk::HTML
  • MIME::Entity
  • MIME::Parser
  • MIME::Types
  • MIME::WordDecoder
  • MIME::Words

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!

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.

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: JaM::Account, JaM::Address, JaM::Config, JaM::Database, JaM::Debug, JaM::Drop, JaM::Filter::IO, JaM::Filter::View, JaM::Folder, JaM::Func, JaM::GUI, JaM::GUI::Account, JaM::GUI::Address, JaM::GUI::Base, JaM::GUI::Component, JaM::GUI::Compose, JaM::GUI::Config, JaM::GUI::Database, JaM::GUI::Folders, JaM::GUI::HTMLSurface, JaM::GUI::IO_Filter, JaM::GUI::Init, JaM::GUI::Mail, JaM::GUI::MailAsHTML, JaM::GUI::MailAsText, JaM::GUI::NetscapeImport, JaM::GUI::Search, JaM::GUI::Subjects, JaM::GUI::Window, JaM::Import::Netscape, JaM::Mail

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
JaM::Account metacpan
JaM::Address metacpan
JaM::Config metacpan
JaM::Database metacpan
JaM::Debug metacpan
JaM::Drop metacpan
JaM::Filter::IO metacpan
JaM::Folder metacpan
JaM::Func metacpan
JaM::GUI metacpan
JaM::GUI::Account metacpan
JaM::GUI::Address metacpan
JaM::GUI::Base metacpan
JaM::GUI::Component metacpan
JaM::GUI::Compose metacpan
JaM::GUI::Config metacpan
JaM::GUI::Database metacpan
JaM::GUI::Folders metacpan
JaM::GUI::HTMLSurface metacpan
JaM::GUI::IO_Filter metacpan
JaM::GUI::Init metacpan
JaM::GUI::Mail metacpan
JaM::GUI::MailAsHTML metacpan
JaM::GUI::MailAsText metacpan
JaM::GUI::NetscapeImport metacpan
JaM::GUI::Search metacpan
JaM::GUI::Subjects metacpan
JaM::GUI::Window metacpan
JaM::Import::Netscape metacpan
JaM::Mail metacpan

Provides

Name File View
JaM::Entity lib/JaM/Mail.pm metacpan
JaM::Filter::IO::Apply lib/JaM/Filter/IO.pm metacpan
JaM::Filter::IO::Rule lib/JaM/Filter/IO.pm metacpan
JaM::Filter::Search::Rule lib/JaM/GUI/Search.pm metacpan

Other Files

Changes metacpan
README metacpan