DBD-mysql 4.023
Kwalitee Issues
- buildtool_not_executable
 - 
        
Change the permissions of Build.PL/Makefile.PL to not-executable.
 - use_strict
 - 
        
Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.
Error: Bundle::DBD::mysql
 - no_pod_errors
 - 
        
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: DBD-mysql-4.023/lib/DBD/mysql.pm -- Around line 1315: '=item' outside of any '=over' Around line 1464: You forgot a '=back' before '=head1' Around line 1727: You forgot a '=back' before '=head1' Around line 2070: Non-ASCII character seen before =encoding in 'K�nig'. Assuming UTF-8
 
- has_meta_json
 - 
        
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
 - use_warnings
 - 
        
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: Bundle::DBD::mysql, DBD::mysql, DBD::mysql::GetInfo
 - consistent_version
 - 
        
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Error: 4.004,4.023
 
- meta_yml_has_provides
 - 
        
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.
 - has_separate_license_file
 - 
        
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
 - has_security_doc
 - 
        
Add SECURITY(.pod|md). See Software::Security::Policy.
 - security_doc_contains_contact
 - 
        
Add SECURITY(.pod|md) and add a contact address. See Software::Security::Policy.
 - has_contributing_doc
 - 
        
Add CONTRIBUTING(.pod|md). See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.