Is unique_by safe to use?

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

What is the latest version of unique_by?

The latest version of unique_by is 3.0.0, released 2014-12-11.

Does unique_by have known vulnerabilities?

No known vulnerabilities on the latest version of unique_by.

Is unique_by deprecated?

No, unique_by is actively maintained. Latest release: 3.0.0 (2014-12-11).

What are alternatives to unique_by?

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

What license does unique_by use?

unique_by is licensed under UNLICENSE.

unique_by

rubygemsv3.0.0

Allows uniqueness of a record when sharding (specifying the shard ID as the group) or span accross tables (receipts).

License UNLICENSEpermissive5 versions1 deps1,126,308 weekly dl

odedniv/unique_by

/ 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

Health History

Dependency Tree

License Audit

Dependencies (1)

generate_method

API access

Get this data programmatically — free, no authentication.

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