Is constant_table_saver safe to use?

constant_table_saver has no known vulnerabilities on the latest version (6.1.0). DepScope rates its health at 48/100 (high risk).

What is the latest version of constant_table_saver?

The latest version of constant_table_saver is 6.1.0, released 2020-11-12.

Does constant_table_saver have known vulnerabilities?

No known vulnerabilities on the latest version of constant_table_saver.

Is constant_table_saver deprecated?

No, constant_table_saver is actively maintained. Latest release: 6.1.0 (2020-11-12).

What are alternatives to constant_table_saver?

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

What license does constant_table_saver use?

constant_table_saver is licensed under MIT.

constant_table_saver

rubygemsv6.1.0

Loads all records from the table on first use, and thereafter returns the cached (and frozen) records for all find calls. Optionally, creates class-level methods you can use to grab the records, named after the name field you specify.

License MITpermissive14 versions1 deps428,578 weekly dl

http://github.com/willbryant/constant_table_saver

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

9/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/constant_table_saver