Is ssl_requirement safe to use?

ssl_requirement has no known vulnerabilities on the latest version (0.1.0). DepScope rates its health at 39/100 (critical risk).

What is the latest version of ssl_requirement?

The latest version of ssl_requirement is 0.1.0, released 2010-01-12.

Does ssl_requirement have known vulnerabilities?

No known vulnerabilities on the latest version of ssl_requirement.

Is ssl_requirement deprecated?

No, ssl_requirement is actively maintained. Latest release: 0.1.0 (2010-01-12).

What are alternatives to ssl_requirement?

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

What license does ssl_requirement use?

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

ssl_requirement

rubygemsv0.1.0

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.

1 versions0 deps436,182 weekly dl

http://github.com/rails/ssl_requirement

39

/ 100

Health

use with caution

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

Low health score (39/100)

Health breakdown

0 – 100

0/25

maintenance

14/20

popularity

25/25

security

0/15

maturity

0/15

community

Vulnerabilities

0

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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