Kwalitee Issues

no_pax_headers

If you use Mac OS X >= 10.6, use gnu tar (/usr/bin/gnutar) to avoid PAX headers. It's also important to rename (shorten) long file names (>= 100 characters) in the distribution.

Error: pax_global_header,pax_global_header

has_readme

Add a README to the distribution. It should contain a quick description of your module and how to install it.

has_manifest

Add a MANIFEST to the distribution. Your buildtool should be able to autogenerate it (eg "make manifest" or "./Build manifest")

has_meta_yml

Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.

has_buildtool

Add a Makefile.PL (for ExtUtils::MakeMaker/Module::Install) or a Build.PL (for Module::Build and its friends), or use a distribution builder such as Dist::Zilla, Dist::Milla, Minilla.

has_proper_version

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'

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.

manifest_matches_dist

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.

has_abstract_in_pod

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.

prereq_matches_use

List all used modules in META.yml requires

Error:

  • Devel::PartialDump
  • List::AllUtils
  • Moose
  • Moose::Meta::Class
  • Moose::Role
  • Moose::Util
  • MooseX::Params::Validate
  • MooseX::Types
  • MooseX::Types::Moose
  • MooseX::Types::Structured
  • Set::Object
  • Sub::Exporter
  • aliased
  • namespace::autoclean

main_module_version_matches_dist_version

Make sure that the main module name and version are the same of the distribution.

no_pod_errors

Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.

Error: ocharles-Test-Magpie-9a8e649/lib/Test/Magpie/ArgumentMatcher.pm -- Around line 100: Unknown directive: =func Around line 107: Unknown directive: =method Around line 112: Unknown directive: =func Around line 122: Unknown directive: =func Around line 127: Unknown directive: =func Around line 133: Unknown directive: =func ocharles-Test-Magpie-9a8e649/lib/Test/Magpie/Invocation.pm -- Around line 13: Unknown directive: =attr Around line 17: Unknown directive: =attr ocharles-Test-Magpie-9a8e649/lib/Test/Magpie/Mock.pm -- Around line 73: Unknown directive: =attr Around line 80: Unknown directive: =attr Around line 86: Unknown directive: =method Around line 90: Unknown directive: =method ocharles-Test-Magpie-9a8e649/lib/Test/Magpie/Role/HasMock.pm -- Around line 17: Unknown directive: =attr ocharles-Test-Magpie-9a8e649/lib/Test/Magpie/Role/MethodCall.pm -- Around line 57: Unknown directive: =method Around line 62: Unknown directive: =method Around line 69: Unknown directive: =attr Around line 73: Unknown directive: =attr ocharles-Test-Magpie-9a8e649/lib/Test/Magpie/Stub.pm -- Around line 67: Unknown directive: =method Around line 72: Unknown directive: =method Around line 77: Unknown directive: =method Around line 81: Unknown directive: =attr ocharles-Test-Magpie-9a8e649/lib/Test/Magpie/Types.pm -- Around line 13: Unknown directive: =type ocharles-Test-Magpie-9a8e649/lib/Test/Magpie/Util.pm -- Around line 28: Unknown directive: =func Around line 33: Unknown directive: =func ocharles-Test-Magpie-9a8e649/lib/Test/Magpie.pm -- Around line 109: Unknown directive: =func Around line 113: Unknown directive: =func Around line 133: Unknown directive: =func Around line 143: Unknown directive: =func Around line 148: Unknown directive: =func Around line 152: Unknown directive: =func

has_meta_json

Add a META.json to the distribution. Your buildtool should be able to autogenerate it.

meta_yml_has_license

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.

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.

test_prereq_matches_use

List all modules used in the test suite in META.yml test_requires

Error:

  • Moose::Role
  • MooseX::Types::Moose
  • Test::Fatal
  • Test::Moose

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.

Modules

Name Abstract Version View
Test::Magpie metacpan
Test::Magpie::ArgumentMatcher metacpan
Test::Magpie::Inspect metacpan
Test::Magpie::Invocation metacpan
Test::Magpie::Meta::Class metacpan
Test::Magpie::Mock metacpan
Test::Magpie::Role::HasMock metacpan
Test::Magpie::Role::MethodCall metacpan
Test::Magpie::Spy metacpan
Test::Magpie::Stub metacpan
Test::Magpie::Types metacpan
Test::Magpie::Util metacpan
Test::Magpie::When metacpan

Other Files

Changes metacpan
dist.ini metacpan