Is transactional_capybara safe to use?

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

What is the latest version of transactional_capybara?

The latest version of transactional_capybara is 0.2.0, released 2017-03-27.

Does transactional_capybara have known vulnerabilities?

No known vulnerabilities on the latest version of transactional_capybara.

Is transactional_capybara deprecated?

No, transactional_capybara is actively maintained. Latest release: 0.2.0 (2017-03-27).

What are alternatives to transactional_capybara?

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

What license does transactional_capybara use?

transactional_capybara is licensed under MIT.

transactional_capybara

rubygemsv0.2.0

Support for DB transactions with Capybara

License MITpermissive6 versions1 deps437,576 weekly dl

/ 100

Health

use with caution

[email protected] low health (45/100) — consider alternatives

Moderate health score (45/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

capybara

API access

Get this data programmatically — free, no authentication.

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