Kwalitee Issues

no_mymeta_files

Update MANIFEST.SKIP to exclude MYMETA files. If you are lazy, add "#!install_default" in your MANIFEST.SKIP and update your ExtUtils::Manifest if necessary, then some of the most common files will be excluded.

valid_signature

Sign the dist as the last step before creating the archive. Take care not to modify/regenerate dist meta files or the manifest.

Error: Old SIGNATURE detected. Please inform the module author to regenerate SIGNATURE using Module::Signature version 0.82 or newer. gpg: Signature made Mon 14 Mar 2005 06:23:52 AM JST gpg: using DSA key 57A79945C57858AD gpg: Can't check signature: No public key --- SIGNATURE Wed Nov 30 15:42:12 2011 +++ @@ -1,11 +1,13 @@ SHA1 308e635e1928d03e6c92ef224557847e18f492a6 BUGS -SHA1 466429e1cefc8de46f7310bc7c64e6ac6af108e0 Build.PL -SHA1 2cb916a845f60e44d62efe689de063d7bef20a99 Changes +SHA1 80df80236398be75d024c036c75dcbc45650c4ae Changes SHA1 efa8cb615886410be8de15f5a6925697f624d278 INSTALL -SHA1 d0e591b2e5eafcc9a8de8ff9eda691fad5f85ffc MANIFEST -SHA1 5c69f53a9cb6f5f717dd1d02266fc7c9f675a902 MANIFEST.SKIP -SHA1 45fa692c1ad1ec954fe181c2d77b674f478a4201 META.yml -SHA1 c88a83fd974fad3c16428163c87d3e6835296ae7 Makefile.PL +SHA1 98b9c363ae32b81f9450e7baf82ba9470c37628d MANIFEST +SHA1 ab641041c2b5d85a7031d8ba3473bd8c42f01bb8 MANIFEST.SKIP +SHA256 927508742b02e75e3cab43b29208c879e0795d387d0a6a4c7a71f70913ae0476 META.json +SHA1 a19e324220107450a700d62f3cf942f272cef1dc META.yml +SHA256 0093a7b2a89b94cdea5805f6eaab1fca1e3764c994a73817b20fd2c486a3447f MYMETA.json +SHA256 db6b9dc34cbb39f0ad8feb12720a047dbae9a09ea928996a7d18b7c159457e2a MYMETA.yml +SHA1 4e481451f94675871b0658d1f654ea8688916c04 Makefile.PL SHA1 0de078a628603bf24ba4d01f2eb004360661be68 README SHA1 8f869f84e72c6fc7ac89ce26326bf981505be467 configure SHA1 8a4e566bff0ad33481975d55bcef13a9244bde16 examples/powers @@ -13,15 +15,15 @@ SHA1 ff6df90436963b2b7e73f8ce6d6327f2dbcad1c3 examples/powers3 SHA1 0fca941997cba7e66d39d4cec737ef09ee7df454 examples/powers4 SHA1 37691f612074aa2fcea31c3b17c6ee46640f43db examples/powers5 -SHA1 cef7ba06dd315bf803d87ab7753ed7b92fb45818 lib/Term/ProgressBar.pm -SHA1 37ba03162a46931b496a18413401d8f25b303cf1 make-pm +SHA256 3c9178c329a0d81dd0822a6e6327d8517a5a8750bfce88de33423b9cae541b32 examples/simple_use.pl +SHA256 599cdd48b868d6cf69d358441d12dd837b084192b1507fb6ab2743d5daa0ead4 examples/smooth_bar.pl +SHA1 218ebb5cdd9c116e24bc539a00cf131bafde7c90 lib/Term/ProgressBar.pm SHA1 e7569e5eeef2a8558e6d4828be087a6e1a841295 t/0-signature.t -SHA1 433e3ecad2aa8a7b3bb2f3766b17c195b33cbcc5 t/compat.t +SHA1 96b5f2188f0170c11378ec92adc20fb5883ff892 t/compat.t -SHA1 f02bc46da7e3c83478c244adfad443f9c1a2b4ca t/eta-linear.t +SHA1 d5cb7f51c62128875c6bd5d22f38e8fce4a92b76 t/eta-linear.t -SHA1 f3b178ae1e9f1f1789443522ac861c8421f93eee t/name.t +SHA1 3ddce6d08154cea2eb7d7d41b9e4ec644165aa1d t/name.t -SHA1 037b2bf330c9ce722c1d122e4e561c610f4fee83 t/test.pm +SHA1 8a09c2e0a40d22229fc0526f8502d41798a331ca t/v1-message.t -SHA1 ab36b1695c7ca9281da620347487bf88d02e66da t/v1-message.t +SHA1 103b5bfbd204e028a2bf998df13f945d6d7f5e72 t/v2-message.t -SHA1 91f9f8f0765d5d7924c4c130934facb91eca6833 t/v2-message.t +SHA1 b995f39dcc7a9488cdf1125ff8d1d36f90a30963 t/v2-mobile.t -SHA1 87ecb3158e5eb9fe020c819e2d2f80ff8be45d92 t/v2-mobile.t +SHA1 89fe9b2c923c15a6a80bb4764e50f1186154e724 t/v2-simple.t -SHA1 119b353912834b0040150a7094bf14425be03936 t/v2-simple.t +SHA1 be5ba15d10609cf3e94d92b6da704433f24209b2 t/zero.t -SHA1 9048c3d6b67959e3cd598ac0e151daff435f39fe t/zero.t ==> MISMATCHED content between SIGNATURE and distribution files! <==

meta_yml_declares_perl_version

If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.

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.

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: Term::ProgressBar

no_unauthorized_packages

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:

  • Term::ProgressBar

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.

meta_yml_has_repository_resource

Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).

has_separate_license_file

This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.

Modules

Name Abstract Version View
Term::ProgressBar provide a progress meter on a standard terminal 2.10 metacpan

Other Files

Changes metacpan
MANIFEST metacpan
META.json metacpan
META.yml metacpan
Makefile.PL metacpan
README metacpan