libapreq2 2.03_04-dev Deleted
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'
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.
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.
Make sure that the main module name and version are the same of the distribution.
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
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.
Use authoring tool like Dist::Zilla, Milla, and Minilla to generate correct provides.
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.