Is has_secure_token safe to use?

has_secure_token has no known vulnerabilities on the latest version (1.0.0). DepScope rates its health at 45/100 (high risk).

What is the latest version of has_secure_token?

The latest version of has_secure_token is 1.0.0, released 2015-04-24.

Does has_secure_token have known vulnerabilities?

No known vulnerabilities on the latest version of has_secure_token.

Is has_secure_token deprecated?

No, has_secure_token is actively maintained. Latest release: 1.0.0 (2015-04-24).

What are alternatives to has_secure_token?

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

What license does has_secure_token use?

has_secure_token is licensed under MIT.

has_secure_token

rubygemsv1.0.0

HasSecureToken provides you an easily way to geneatre uniques random tokens for any model in ruby on rails. **SecureRandom::base58** is used to generate the 24-character unique token, so collisions are highly unlikely.

License MITpermissive3 versions1 deps2,461,248 weekly dl

robertomiranda/has_secure_token

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Quality signals

OSS Criticality

0.42medium

Health History

Dependency Tree

License Audit

Dependencies (1)

activerecord

API access

Get this data programmatically — free, no authentication.

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