Is POE-Component-Client-Whois safe to use?

POE-Component-Client-Whois has no known vulnerabilities on the latest version (1.38). DepScope rates its health at 27/100 (critical risk).

What is the latest version of POE-Component-Client-Whois?

The latest version of POE-Component-Client-Whois is 1.38, released 2020-07-15.

Does POE-Component-Client-Whois have known vulnerabilities?

No known vulnerabilities on the latest version of POE-Component-Client-Whois.

Is POE-Component-Client-Whois deprecated?

No, POE-Component-Client-Whois is actively maintained. Latest release: 1.38 (2020-07-15).

What are alternatives to POE-Component-Client-Whois?

DepScope has no curated alternatives for POE-Component-Client-Whois at this time.

What license does POE-Component-Client-Whois use?

POE-Component-Client-Whois is licensed under perl_5.

POE-Component-Client-Whois

cpanv1.38

A one shot non-blocking RFC 812 WHOIS query.

License perl_51 versions1 maintainers16 deps

bingos/poe-component-client-whois

/ 100

Health

use with caution

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

Low health score (27/100)

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 (16)

Test::Pod Pod::Coverage::TrustPod Test::Pod::Coverage POE::Wheel::SocketFactory Net::Netmask Net::IP::Minimal POE POE::Wheel::ReadWrite POE::Filter::Line Socket Carp ExtUtils::MakeMaker IPC::Open3 Test::More IO::Handle File::Spec

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cpan/POE-Component-Client-Whois

Last updated · 2020-07-15T18:54:10