Is MooseX-Meta-TypeConstraint-ForceCoercion safe to use?

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

What is the latest version of MooseX-Meta-TypeConstraint-ForceCoercion?

The latest version of MooseX-Meta-TypeConstraint-ForceCoercion is 0.01, released 2009-04-13.

Does MooseX-Meta-TypeConstraint-ForceCoercion have known vulnerabilities?

No known vulnerabilities on the latest version of MooseX-Meta-TypeConstraint-ForceCoercion.

Is MooseX-Meta-TypeConstraint-ForceCoercion deprecated?

No, MooseX-Meta-TypeConstraint-ForceCoercion is actively maintained. Latest release: 0.01 (2009-04-13).

What are alternatives to MooseX-Meta-TypeConstraint-ForceCoercion?

DepScope has no curated alternatives for MooseX-Meta-TypeConstraint-ForceCoercion at this time.

What license does MooseX-Meta-TypeConstraint-ForceCoercion use?

MooseX-Meta-TypeConstraint-ForceCoercion is licensed under perl_5.

MooseX-Meta-TypeConstraint-ForceCoercion

cpanv0.01

Force coercion when validating type constraints

License perl_51 versions1 maintainers2 deps

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

Moose namespace::autoclean

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cpan/MooseX-Meta-TypeConstraint-ForceCoercion

Last updated · 2009-04-13T02:19:10