Is activerecord-delay_touching safe to use?

activerecord-delay_touching has no known vulnerabilities on the latest version (1.1.0). DepScope rates its health at 41/100 (high risk).

What is the latest version of activerecord-delay_touching?

The latest version of activerecord-delay_touching is 1.1.0, released 2018-08-24.

Does activerecord-delay_touching have known vulnerabilities?

No known vulnerabilities on the latest version of activerecord-delay_touching.

Is activerecord-delay_touching deprecated?

No, activerecord-delay_touching is actively maintained. Latest release: 1.1.0 (2018-08-24).

What are alternatives to activerecord-delay_touching?

Popular alternatives to activerecord-delay_touching in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does activerecord-delay_touching use?

activerecord-delay_touching is licensed under MIT.

activerecord-delay_touching

rubygemsv1.1.0

Batch up your ActiveRecord "touch" operations for better performance. ActiveRecord::Base.delay_touching do ... end. When "end" is reached, all accumulated "touch" calls will be consolidated into as few database round trips as possible.

License MITpermissive7 versions1 deps70,900 weekly dl

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

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/activerecord-delay_touching