Crypt-Util 0.11 Latest
Kwalitee Issues
- meta_yml_conforms_to_known_spec
-
Take a look at the META.yml Spec at https://metacpan.org/pod/CPAN::Meta::History::Meta_1_4 (for version 1.4) or https://metacpan.org/pod/CPAN::Meta::Spec (for version 2), and change your META.yml accordingly.
Error: License 'MIT' is invalid (license) [Validation: 1.4]
- has_readme
-
Add a README to the distribution. It should contain a quick description of your module and how to install it.
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Crypt-Util-0.11/lib/Crypt/Util.pm -- Around line 1163: You can't have =items (as at line 1167) unless the first thing after the =over is an =item Around line 1520: You forgot a '=back' before '=head1' Around line 1580: Expected '=item *' Around line 1589: Expected '=item *' Around line 1642: =back without =over Around line 1684: You forgot a '=back' before '=head1'
- 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 Thu 27 May 2010 06:57:45 PM JST gpg: using DSA key 542C11C0EBD27418 gpg: Can't check signature: No public key ==> BAD/TAMPERED signature detected! <==
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- 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.
- 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.