Bundle-Bricolage 1.11.0 Latest
Kwalitee Issues
- 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: Bundle::Bricolage
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Bundle-Bricolage-1.11.0/lib/Bundle/Bricolage.pm -- Around line 142: Non-ASCII character seen before =encoding in 'generalâutility'. Assuming UTF-8
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- 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: Bundle::Bricolage
- 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.
- 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 |
---|---|---|---|
Bundle::Bricolage | Modules required to run Bricolage content management system. | 1.11.0 | metacpan |