Is multi_fetch_fragments safe to use?

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

What is the latest version of multi_fetch_fragments?

The latest version of multi_fetch_fragments is 0.0.17, released 2013-07-31.

Does multi_fetch_fragments have known vulnerabilities?

No known vulnerabilities on the latest version of multi_fetch_fragments.

Is multi_fetch_fragments deprecated?

No, multi_fetch_fragments is actively maintained. Latest release: 0.0.17 (2013-07-31).

What are alternatives to multi_fetch_fragments?

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

What license does multi_fetch_fragments use?

License information for multi_fetch_fragments is not declared in the registry metadata.

multi_fetch_fragments

rubygemsv0.0.17

multi_fetch_fragments allows you to render a collection of partials through Rails multi read caching mechanism.

16 versions0 deps508,747 weekly dl

/ 100

Health

use with caution

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

Moderate health score (48/100) — verify manually

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

API access

Get this data programmatically — free, no authentication.

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