Is order_as_specified safe to use?

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

What is the latest version of order_as_specified?

The latest version of order_as_specified is 1.7, released 2021-02-26.

Does order_as_specified have known vulnerabilities?

No known vulnerabilities on the latest version of order_as_specified.

Is order_as_specified deprecated?

No, order_as_specified is actively maintained. Latest release: 1.7 (2021-02-26).

What are alternatives to order_as_specified?

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

What license does order_as_specified use?

order_as_specified is licensed under MIT.

order_as_specified

rubygemsv1.7

Obtain ActiveRecord results with a custom ordering with no need to store anything in the database.

License MITpermissive9 versions1 deps2,617,106 weekly dl

panorama-ed/order_as_specified

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Quality signals

OSS Criticality

0.43medium

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/order_as_specified