Is transaction_retry safe to use?

transaction_retry has no known vulnerabilities on the latest version (1.0.3). DepScope rates its health at 47/100 (high risk).

What is the latest version of transaction_retry?

The latest version of transaction_retry is 1.0.3, released 2018-06-18.

Does transaction_retry have known vulnerabilities?

No known vulnerabilities on the latest version of transaction_retry.

Is transaction_retry deprecated?

No, transaction_retry is actively maintained. Latest release: 1.0.3 (2018-06-18).

What are alternatives to transaction_retry?

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

What license does transaction_retry use?

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

transaction_retry

rubygemsv1.0.3

Retries database transaction on deadlock and transaction serialization errors. Supports MySQL, PostgreSQL and SQLite (as long as you are using new drivers mysql2, pg, sqlite3).

3 versions2 deps1,511,527 weekly dl

qertoip/transaction_retry

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

activerecord transaction_isolation

API access

Get this data programmatically — free, no authentication.

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