Kwalitee Issues

meta_yml_conforms_to_known_spec

Take a look at the META.yml Spec at https://metacpan.org/pod/CPAN::Meta::History::Meta_1_4 (for version 1.4) or https://metacpan.org/pod/CPAN::Meta::Spec (for version 2), and change your META.yml accordingly.

Error: Expected a list structure (author) [Validation: 1.3];License '<undef>' is invalid (license) [Validation: 1.3];Missing mandatory field, 'abstract' (abstract) [Validation: 1.3];Missing mandatory field, 'author' (author) [Validation: 1.3];Missing mandatory field, 'license' (license) [Validation: 1.3];value is an undefined string (abstract) [Validation: 1.3]

buildtool_not_executable

Change the permissions of Build.PL/Makefile.PL to not-executable.

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.

has_meta_json

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

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, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.

Error: Lingua::JA::Romanize::Base, Lingua::JA::Romanize::DictJA, Lingua::JA::Romanize::Japanese, Lingua::JA::Romanize::Juman, Lingua::JA::Romanize::Kana, Lingua::JA::Romanize::Kana::Hepburn, Lingua::JA::Romanize::MeCab

consistent_version

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

Error: 0.20,0.22,0.23

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
Lingua::JA::Romanize::Base Baseclass for Lingua::JA::Romanize::* modules 0.20 metacpan
Lingua::JA::Romanize::DictJA Dictionary converter 0.23 metacpan
Lingua::JA::Romanize::Japanese Romanization of Japanese language 0.23 metacpan
Lingua::JA::Romanize::Juman Romanization of Japanese language with JUMAN 0.20 metacpan
Lingua::JA::Romanize::Kana Romanization of Japanese Hiragana/Katakana 0.22 metacpan
Lingua::JA::Romanize::Kana::Hepburn Hepburn Romanization using Japanese passport rules 0.20 metacpan
Lingua::JA::Romanize::MeCab Romanization of Japanese language with MeCab 0.20 metacpan

Provides

Name File View
Lingua::JA::Romanize::MeCab::EUC lib/Lingua/JA/Romanize/MeCab.pm metacpan
Lingua::JA::Romanize::MeCab::SJIS lib/Lingua/JA/Romanize/MeCab.pm metacpan
Lingua::JA::Romanize::MeCab::UTF8 lib/Lingua/JA/Romanize/MeCab.pm metacpan

Other Files

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