Is otp-jwt safe to use?

otp-jwt has no known vulnerabilities on the latest version (0.3.1). DepScope rates its health at 74/100 (moderate risk).

What is the latest version of otp-jwt?

The latest version of otp-jwt is 0.3.1, released 2021-10-12.

Does otp-jwt have known vulnerabilities?

No known vulnerabilities on the latest version of otp-jwt.

Is otp-jwt deprecated?

No, otp-jwt is actively maintained. Latest release: 0.3.1 (2021-10-12).

What are alternatives to otp-jwt?

Popular alternatives to otp-jwt in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

otp-jwt

rubygemsv0.3.1

OTP (email, SMS) JWT authentication for HTTP APIs.

License MITpermissive11 versions3 deps315,261 weekly dl

stas/otp-jwt

/ 100

Health

safe to use

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

Health breakdown0 – 100

25/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

1/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (3)

activesupport jwt rotp

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/otp-jwt

otp-jwt

rubygemsv0.3.1

OTP (email, SMS) JWT authentication for HTTP APIs.

License MITpermissive11 versions3 deps315,261 weekly dl

stas/otp-jwt

/ 100

Health

safe to use

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

Health breakdown0 – 100

25/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

1/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (3)

activesupport jwt rotp

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/otp-jwt