Is consistency_fail safe to use?

consistency_fail has no known vulnerabilities on the latest version (0.3.7). DepScope rates its health at 48/100 (high risk).

What is the latest version of consistency_fail?

The latest version of consistency_fail is 0.3.7, released 2018-10-22.

Does consistency_fail have known vulnerabilities?

No known vulnerabilities on the latest version of consistency_fail.

Is consistency_fail deprecated?

No, consistency_fail is actively maintained. Latest release: 0.3.7 (2018-10-22).

What are alternatives to consistency_fail?

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

What license does consistency_fail use?

consistency_fail is licensed under MIT.

consistency_fail

rubygemsv0.3.7

With more than one application server, validates_uniqueness_of becomes a lie. Two app servers -> two requests -> two near-simultaneous uniqueness checks -> two processes that commit to the database independently, violating this faux constraint. You'll need a database-level constraint for cases like these. consistency_fail will find your missing unique indexes, so you can add them and stop ignoring the C in ACID.

License MITpermissive13 versions0 deps736,937 weekly dl

http://github.com/trptcolin/consistency_fail

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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