Is rufus-tokyo safe to use?

rufus-tokyo has no known vulnerabilities on the latest version (1.0.7). DepScope rates its health at 44/100 (high risk).

What is the latest version of rufus-tokyo?

The latest version of rufus-tokyo is 1.0.7, released 2010-02-10.

Does rufus-tokyo have known vulnerabilities?

No known vulnerabilities on the latest version of rufus-tokyo.

Is rufus-tokyo deprecated?

No, rufus-tokyo is actively maintained. Latest release: 1.0.7 (2010-02-10).

What are alternatives to rufus-tokyo?

Popular alternatives to rufus-tokyo in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does rufus-tokyo use?

License information for rufus-tokyo is not declared in the registry metadata.

rufus-tokyo

rubygemsv1.0.7

Ruby-ffi based lib to access Tokyo Cabinet and Tyrant. The ffi-based structures are available via the Rufus::Tokyo namespace. There is a Rufus::Edo namespace that interfaces with Hirabayashi-san's native Ruby interface, and whose API is equal to the Rufus::Tokyo one. Finally rufus-tokyo includes ffi-based interfaces to Tokyo Dystopia (thanks to Jeremy Hinegardner).

20 versions0 deps44,000 weekly dl

http://github.com/jmettraux/rufus-tokyo/

/ 100

Health

use with caution

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

Moderate health score (44/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

10/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/rufus-tokyo