Kwalitee Issues


Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.


Add =head1 LICENSE and the text of the license to the main module in your code.


Take a look at the META.yml Spec at (for version 1.4) or (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]


Fix the version(s).


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

Error: 10474,10819,10837,3667,7868,9914,9934


Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.


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


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.


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.


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: App::Repository, App::Repository::DBI, App::Repository::File, App::Repository::MySQL, App::RepositoryObject, App::SessionObject::RepositoryObjectDomain, App::SessionObject::RepositoryObjectSet, App::ValueDomain::Repository


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


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.


Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).


Name Abstract Version View
App::Repository Logical data access layer for the App::Context Framework, providing a uniform API to access data in databases, file systems, remote web sites, etc. 10819 metacpan
App::Repository::DBI a repository which relies on a DBI interface to a relational database (no caching) 10837 metacpan
App::Repository::File a repository which stores its data in flat files 3667 metacpan
App::Repository::MySQL a MySQL database, accessed through the Repository interface 10474 metacpan
App::RepositoryObject Interface for data persistence 7868 metacpan
App::SessionObject::RepositoryObjectDomain 9934 metacpan
App::SessionObject::RepositoryObjectSet A set of repository objects described by a set of query parameters 9934 metacpan
App::ValueDomain::Repository 9914 metacpan

Other Files

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