Kwalitee Issues

has_license_in_source_file

Add =head1 LICENSE and the text of the license to the main module in your code.

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.

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: gpg: Signature made Thu 13 Apr 2023 04:23:15 PM JST gpg: using RSA key 6C488EC126A0B2084A70E37AA2357D4697BF07CB gpg: Can't check signature: No public key --- SIGNATURE Thu Apr 13 16:23:15 2023 +++ @@ -1,5 +1,5 @@ SHA256 db4665fef05e4c5ce78dd3b8df97ef09b4fc85fe7d087a2cf0933f319b5f5571 Backend.pm -SHA256 49d31cfa9fcbc8b93f59a7a274e0a1d2e658a06c8feda4b73cc379f3caa14827 Changes +SHA256 9d40aac50f538ebfc3bdae51cdc1ee702aded7ed338b847db98a48be07daaa0e Changes SHA256 74ebf9b47f1d6aa16ebf0624b2f21d88e031a484aaf242ff7ffc44f3c9dfd92e LICENSE SHA256 15c11093fed8d546f9cf89cd8fb3a5a6412a3ab1782a0d814284518b5ff5987f MANIFEST SHA256 00f67b6047ad46e13259cb8425408ff297273fdaca52578236745b8ce0de6570 META.yml ==> MISMATCHED content between SIGNATURE and distribution files! <==

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.

Modules

Name Abstract Version View
Wikibase::Cache::Backend 0.03 metacpan

Other Files

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