Is Algorithm::LossyCount safe to use?

Algorithm::LossyCount has no known vulnerabilities on the latest version (0.03). DepScope rates its health at 27/100 (critical risk).

What is the latest version of Algorithm::LossyCount?

The latest version of Algorithm::LossyCount is 0.03, released 2014-03-18.

Does Algorithm::LossyCount have known vulnerabilities?

No known vulnerabilities on the latest version of Algorithm::LossyCount.

Is Algorithm::LossyCount deprecated?

No, Algorithm::LossyCount is actively maintained. Latest release: 0.03 (2014-03-18).

What are alternatives to Algorithm::LossyCount?

DepScope has no curated alternatives for Algorithm::LossyCount at this time.

What license does Algorithm::LossyCount use?

Algorithm::LossyCount is licensed under mit.

Algorithm::LossyCount

cpanv0.03

Memory-efficient approximate frequency count.

License mitpermissive1 versions1 maintainers6 deps

git://github.com/sekia/Algorithm-LossyCount

/ 100

Health

use with caution

Algorithm::[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 (6)

POSIX Carp Test::Exception::LessClever Test::More List::Util ExtUtils::MakeMaker

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cpan/Algorithm::LossyCount

Last updated · 2014-03-18T03:35:45