Is MooseX-Attribute-TypeConstraint-CustomizeFatal safe to use?

MooseX-Attribute-TypeConstraint-CustomizeFatal has no known vulnerabilities on the latest version (0.03). DepScope rates its health at 27/100 (critical risk).

Does MooseX-Attribute-TypeConstraint-CustomizeFatal have known vulnerabilities?

No known vulnerabilities on the latest version of MooseX-Attribute-TypeConstraint-CustomizeFatal.

Is MooseX-Attribute-TypeConstraint-CustomizeFatal deprecated?

No, MooseX-Attribute-TypeConstraint-CustomizeFatal is actively maintained. Latest release: 0.03 (2013-07-04).

What are alternatives to MooseX-Attribute-TypeConstraint-CustomizeFatal?

DepScope has no curated alternatives for MooseX-Attribute-TypeConstraint-CustomizeFatal at this time.

What license does MooseX-Attribute-TypeConstraint-CustomizeFatal use?

MooseX-Attribute-TypeConstraint-CustomizeFatal is licensed under perl_5.

MooseX-Attribute-TypeConstraint-CustomizeFatal

cpanv0.03

Control how failed type constraint checks are handled

License perl_51 versions1 maintainers12 deps

http://github.com/avar/moosex-attribute-typeconstraint-customizefatal

/ 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 (12)

ExtUtils::MakeMaker Carp MooseX::Types MooseX::Types::Moose Moose::Role Try::Tiny warnings strict File::Temp File::Find Test::More Moose

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cpan/MooseX-Attribute-TypeConstraint-CustomizeFatal

Last updated · 2013-07-04T15:19:52