Is POE-Component-Jabber safe to use?

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

What is the latest version of POE-Component-Jabber?

The latest version of POE-Component-Jabber is 3.00, released 2009-03-22.

Does POE-Component-Jabber have known vulnerabilities?

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

Is POE-Component-Jabber deprecated?

No, POE-Component-Jabber is actively maintained. Latest release: 3.00 (2009-03-22).

What are alternatives to POE-Component-Jabber?

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

What license does POE-Component-Jabber use?

POE-Component-Jabber is licensed under open_source.

POE-Component-Jabber

cpanv3.00

A POE Component for communicating over Jabber

License open_source1 versions1 maintainers7 deps

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

Digest::SHA1 Authen::SASL POE POE::Component::SSLify POE::Component::PubSub MIME::Base64 POE::Filter::XML

API access

Get this data programmatically — free, no authentication.

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

Last updated · 2009-03-22T08:51:45