Brasil-Checar-CGC 1.01a Latest
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.
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.
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
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 README to the distribution. It should contain a quick description of your module and how to install it.
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.
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Brasil/Checar/CGC/CGC.pm-- Around line 148: Non-ASCII character seen before =encoding in 'ExtensÃ£o'. Assuming CP1252
Fix the version(s).
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.
Add tests or move tests.pl to the t/ directory!
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.
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.
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.
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.