Is two_factor_authentication safe to use?

two_factor_authentication has no known vulnerabilities on the latest version (2.2.0). DepScope rates its health at 51/100 (high risk).

What is the latest version of two_factor_authentication?

The latest version of two_factor_authentication is 2.2.0, released 2019-01-29.

Does two_factor_authentication have known vulnerabilities?

No known vulnerabilities on the latest version of two_factor_authentication.

Is two_factor_authentication deprecated?

No, two_factor_authentication is actively maintained. Latest release: 2.2.0 (2019-01-29).

What are alternatives to two_factor_authentication?

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

What license does two_factor_authentication use?

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

two_factor_authentication

rubygemsv2.2.0

### Features ### * control sms code pattern * configure max login attempts * per user level control if he really need two factor authentication * your own sms logic

13 versions5 deps4,431,656 weekly dl

Houdini/two_factor_authentication

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Maintainer trust

Active maintainers (3m)

1

Contributors (12m)

0

Primary author dominance

0%

GitHub stars

402

single active maintainer 3m

Quality signals

OSS Criticality

0.44medium

Health History

Dependency Tree

License Audit

Dependencies (5)

devise encryptor rails randexp rotp

API access

Get this data programmatically — free, no authentication.

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