GDTextUtil 0.86 Latest
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
Make sure that the main module name and version are the same of the distribution.
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: *** ERROR: =pod directives shouldn't be over one line long! Ignoring all 20 lines of content at line 197 in file GDTextUtil-0.86/Text.pm *** ERROR: unresolved internal link 'font_path' at line 118 in file GDTextUtil-0.86/Text.pm
List all used modules in META.yml requires
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
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.
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.
List all modules used in the test suite in META.yml test_requires
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: GD::Text, GD::Text::Align, GD::Text::Wrap
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.