Data-Dump 1.25 Latest
Kwalitee Issues
- has_human_readable_license
 - 
        
Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
 - has_license_in_source_file
 - 
        
Add =head1 LICENSE and the text of the license to the main module in your code.
 - 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: Data::Dump::FilterContext, Data::Dump::Filtered
 
- has_known_license_in_source_file
 - 
        
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
 - 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: Data::Dump, Data::Dump::FilterContext, Data::Dump::Filtered, Data::Dump::Trace
 - consistent_version
 - 
        
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Error: 0.02,1.25
 
- 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.