Is HTTP::Response::Encoding safe to use?

HTTP::Response::Encoding has no known vulnerabilities on the latest version (0.06). DepScope rates its health at 27/100 (critical risk).

What is the latest version of HTTP::Response::Encoding?

The latest version of HTTP::Response::Encoding is 0.06, released 2009-07-28.

Does HTTP::Response::Encoding have known vulnerabilities?

No known vulnerabilities on the latest version of HTTP::Response::Encoding.

Is HTTP::Response::Encoding deprecated?

No, HTTP::Response::Encoding is actively maintained. Latest release: 0.06 (2009-07-28).

What are alternatives to HTTP::Response::Encoding?

DepScope has no curated alternatives for HTTP::Response::Encoding at this time.

What license does HTTP::Response::Encoding use?

HTTP::Response::Encoding is licensed under unknown.

HTTP::Response::Encoding

cpanv0.06

Adds encoding() to HTTP::Response

License unknown1 versions1 maintainers4 deps

/ 100

Health

use with caution

HTTP::Response::[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 (4)

ExtUtils::MakeMaker Encode Test::More HTTP::Response

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cpan/HTTP::Response::Encoding

Last updated · 2009-07-28T21:29:51