Is POE::Component::Server::Time safe to use?

POE::Component::Server::Time has no known vulnerabilities on the latest version (1.16). DepScope rates its health at 27/100 (critical risk).

What is the latest version of POE::Component::Server::Time?

The latest version of POE::Component::Server::Time is 1.16, released 2017-02-26.

Does POE::Component::Server::Time have known vulnerabilities?

No known vulnerabilities on the latest version of POE::Component::Server::Time.

Is POE::Component::Server::Time deprecated?

No, POE::Component::Server::Time is actively maintained. Latest release: 1.16 (2017-02-26).

What are alternatives to POE::Component::Server::Time?

DepScope has no curated alternatives for POE::Component::Server::Time at this time.

What license does POE::Component::Server::Time use?

POE::Component::Server::Time is licensed under perl_5.

POE::Component::Server::Time

cpanv1.16

A POE component that implements an RFC 868 Time server.

License perl_51 versions1 maintainers10 deps

bingos/poe-component-server-time

/ 100

Health

use with caution

POE::Component::Server::[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 (10)

Test::More File::Spec IO::Handle IPC::Open3 Pod::Coverage::TrustPod Test::Pod Test::Pod::Coverage ExtUtils::MakeMaker POE::Component::Server::Echo POE

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cpan/POE::Component::Server::Time

Last updated · 2017-02-26T18:56:56