Does Perl-Critic-Policy-logicLAB-RequirePackageNamePattern have known vulnerabilities?

No known vulnerabilities on the latest version of Perl-Critic-Policy-logicLAB-RequirePackageNamePattern.

What are alternatives to Perl-Critic-Policy-logicLAB-RequirePackageNamePattern?

DepScope has no curated alternatives for Perl-Critic-Policy-logicLAB-RequirePackageNamePattern at this time.

What license does Perl-Critic-Policy-logicLAB-RequirePackageNamePattern use?

Perl-Critic-Policy-logicLAB-RequirePackageNamePattern is licensed under artistic_2.

Perl-Critic-Policy-logicLAB-RequirePackageNamePattern

cpanv0.05

simple policy for enforcing a package naming policy

License artistic_2permissive1 versions1 maintainers17 deps

jonasbn/pcplrpnp

/ 100

Health

use with caution

[email protected] low health (27/100) — consider alternatives

Moderate health score (27/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

0/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (17)

Module::Build Test::Class Pod::Coverage::TrustPod Test::Pod::Coverage Test::Kwalitee Test::Pod Test::Perl::Critic Test::More IO::Handle IPC::Open3 File::Spec Data::Dumper Perl::Critic::Utils Perl::Critic::Policy Carp Test::CPAN::Changes ExtUtils::MakeMaker

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cpan/Perl-Critic-Policy-logicLAB-RequirePackageNamePattern

Last updated · 2015-08-27T16:03:52