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 '<undef>' is invalid (license) [Validation: 1.3];Missing mandatory field, 'abstract' (abstract) [Validation: 1.3];Missing mandatory field, 'license' (license) [Validation: 1.3];value is an undefined string (abstract) [Validation: 1.3]

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: CSS::Prepare::Plugin::TestPlugins

no_pod_errors

Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.

Error: CSS-Prepare-v0.9.2/lib/CSS/Prepare/Plugin/Contain.pm -- Around line 192: =over without closing =back

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.

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.

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: CSS::Prepare::Plugin::TestPlugins

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
CSS::Prepare pre-process cascading style sheets to make them ready for deployment 0.009002 metacpan
CSS::Prepare::CSSGrammar metacpan
CSS::Prepare::Plugin::BorderRadius metacpan
CSS::Prepare::Plugin::Contain metacpan
CSS::Prepare::Plugin::Opacity metacpan
CSS::Prepare::Plugin::TestPlugins metacpan
CSS::Prepare::Property::Background metacpan
CSS::Prepare::Property::Border metacpan
CSS::Prepare::Property::BorderRadius metacpan
CSS::Prepare::Property::Color metacpan
CSS::Prepare::Property::Effects metacpan
CSS::Prepare::Property::Expansions metacpan
CSS::Prepare::Property::Font metacpan
CSS::Prepare::Property::Formatting metacpan
CSS::Prepare::Property::Generated metacpan
CSS::Prepare::Property::Hacks metacpan
CSS::Prepare::Property::Margin metacpan
CSS::Prepare::Property::Padding metacpan
CSS::Prepare::Property::Tables metacpan
CSS::Prepare::Property::Text metacpan
CSS::Prepare::Property::UI metacpan
CSS::Prepare::Property::Values metacpan
CSS::Prepare::Property::Vendor metacpan

Other Files

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