Jcode 0.30
- Released by
- DANKOGAI
- Version
- Release Date
- 1999-07-13
- Kwalitee
- 137.5
- Core Kwalitee
- 90.62
- LINKS
Jcode 0.30 Deleted
Kwalitee Issues
- has_meta_yml
-
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
- 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: Jcode::Unicode::Constants
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Jcode-0.30/Jcode/H2Z.pm -- Around line 119: '=item' outside of any '=over' =over without closing =back Jcode-0.30/Jcode.pm -- Around line 184: You forgot a '=back' before '=head2' Around line 190: '=item' outside of any '=over' Around line 229: You forgot a '=back' before '=head2' Around line 233: '=item' outside of any '=over' Around line 266: You forgot a '=back' before '=head2' Around line 270: '=item' outside of any '=over' Around line 285: You forgot a '=back' before '=head2' Around line 289: '=item' outside of any '=over' Around line 311: You forgot a '=back' before '=head1' Around line 313: '=item' outside of any '=over' Around line 536: You forgot a '=back' before '=head1'
- 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.
- 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: Jcode, Jcode, Jcode::Constants, Jcode::H2Z, Jcode::Tr, Jcode::Unicode::Constants
- 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.