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.

Error: contrib/stdio/Stdio.pm, contrib/automated_pp_test/pipe_a_command.pm, contrib/automated_pp_test/prior_to_test.pm, contrib/automated_pp_test/remove_file_and_try_executable_again.pm, contrib/automated_pp_test/test_in_further_subdir.pm

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: pipe_a_command, prior_to_test, remove_file_and_try_executable_again, test_in_further_subdir

Ask the owner of the distribution (the one who released it first, or the one who is designated in x_authority) to give you a (co-)maintainer's permission.

Error:

• MainWindow
• Tk::Stdio
• Tk::Stdio::Handle
• pipe_a_command
• prior_to_test
• remove_file_and_try_executable_again
• test_in_further_subdir

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

Error: 0.03,0.06,0.07,0.91,0.975,0.992,1.0,1.035_001

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).