Is bartt-ssl_requirement safe to use?

bartt-ssl_requirement has no known vulnerabilities on the latest version (1.4.2). DepScope rates its health at 48/100 (high risk).

What is the latest version of bartt-ssl_requirement?

The latest version of bartt-ssl_requirement is 1.4.2, released 2012-03-24.

Does bartt-ssl_requirement have known vulnerabilities?

No known vulnerabilities on the latest version of bartt-ssl_requirement.

Is bartt-ssl_requirement deprecated?

No, bartt-ssl_requirement is actively maintained. Latest release: 1.4.2 (2012-03-24).

What are alternatives to bartt-ssl_requirement?

Popular alternatives to bartt-ssl_requirement in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does bartt-ssl_requirement use?

License information for bartt-ssl_requirement is not declared in the registry metadata.

bartt-ssl_requirement

rubygemsv1.4.2

SSL requirement adds a declarative way of specifying that certain actions should only be allowed to run under SSL, and if they're accessed without it, they should be redirected.

13 versions0 deps465,696 weekly dl

http://github.com/bartt/ssl_requirement

/ 100

Health

use with caution

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

Moderate health score (48/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/bartt-ssl_requirement