Is transaction_isolation safe to use?

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

What is the latest version of transaction_isolation?

The latest version of transaction_isolation is 1.0.5, released 2018-06-18.

Does transaction_isolation have known vulnerabilities?

No known vulnerabilities on the latest version of transaction_isolation.

Is transaction_isolation deprecated?

No, transaction_isolation is actively maintained. Latest release: 1.0.5 (2018-06-18).

What are alternatives to transaction_isolation?

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

What license does transaction_isolation use?

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

transaction_isolation

rubygemsv1.0.5

Set transaction isolation level in the ActiveRecord in a database agnostic way. Works with MySQL, PostgreSQL and SQLite as long as you are using new adapters mysql2, pg or sqlite3. Supports all ANSI SQL isolation levels: :serializable, :repeatable_read, :read_committed, :read_uncommitted.

4 versions1 deps2,071,399 weekly dl

qertoip/transaction_isolation

/ 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/transaction_isolation