Is ltree_hierarchy safe to use?

ltree_hierarchy has no known vulnerabilities on the latest version (2.0.0). DepScope rates its health at 41/100 (high risk).

What is the latest version of ltree_hierarchy?

The latest version of ltree_hierarchy is 2.0.0, released 2019-10-30.

Does ltree_hierarchy have known vulnerabilities?

No known vulnerabilities on the latest version of ltree_hierarchy.

Is ltree_hierarchy deprecated?

No, ltree_hierarchy is actively maintained. Latest release: 2.0.0 (2019-10-30).

What are alternatives to ltree_hierarchy?

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

What license does ltree_hierarchy use?

ltree_hierarchy is licensed under MIT.

ltree_hierarchy

rubygemsv2.0.0

Organizes ActiveRecord models into a tree/hierarchy using a materialized path implementation based around PostgreSQL's ltree datatype. ltree's operators ensure that queries are fast and easily understood.

License MITpermissive7 versions2 deps23,597 weekly dl

Leadformance/ltree_hierarchy

/ 100

Health

use with caution

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

Moderate health score (41/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

activerecord pg

API access

Get this data programmatically — free, no authentication.

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