Is tkh_authentication safe to use?

tkh_authentication has no known vulnerabilities on the latest version (0.9.17.2). DepScope rates its health at 40/100 (high risk).

What is the latest version of tkh_authentication?

The latest version of tkh_authentication is 0.9.17.2, released 2014-09-23.

Does tkh_authentication have known vulnerabilities?

No known vulnerabilities on the latest version of tkh_authentication.

Is tkh_authentication deprecated?

No, tkh_authentication is actively maintained. Latest release: 0.9.17.2 (2014-09-23).

What are alternatives to tkh_authentication?

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

What license does tkh_authentication use?

tkh_authentication is licensed under MIT.

tkh_authentication

rubygemsv0.9.17.2

A Rails engine for access control authentication customized for Ten Thousand Hours.

License MITpermissive20 versions4 deps4,011 weekly dl

allesklar/tkh_authentication

/ 100

Health

safe to use

[email protected] is safe to use (health: 40/100)

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (4)

bcrypt rails simple_form stringex

API access

Get this data programmatically — free, no authentication.

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