Is handle_invalid_percent_encoding_requests safe to use?

handle_invalid_percent_encoding_requests has no known vulnerabilities on the latest version (1.1.1). DepScope rates its health at 42/100 (high risk).

What is the latest version of handle_invalid_percent_encoding_requests?

The latest version of handle_invalid_percent_encoding_requests is 1.1.1, released 2022-02-22.

Does handle_invalid_percent_encoding_requests have known vulnerabilities?

No known vulnerabilities on the latest version of handle_invalid_percent_encoding_requests.

Is handle_invalid_percent_encoding_requests deprecated?

No, handle_invalid_percent_encoding_requests is actively maintained. Latest release: 1.1.1 (2022-02-22).

What are alternatives to handle_invalid_percent_encoding_requests?

Popular alternatives to handle_invalid_percent_encoding_requests in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does handle_invalid_percent_encoding_requests use?

handle_invalid_percent_encoding_requests is licensed under MIT.

handle_invalid_percent_encoding_requests

rubygemsv1.1.1

Render 400 error whenever a request's %-encoding is malformed

License MITpermissive5 versions2 deps147,396 weekly dl

http://github.com/sunny/handle_invalid_percent_encoding_requests

/ 100

Health

use with caution

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

Moderate health score (42/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

rack-utf8_sanitizer rails

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/handle_invalid_percent_encoding_requests