Is dirty-memoize safe to use?

dirty-memoize has no known vulnerabilities on the latest version (0.0.4). DepScope rates its health at 42/100 (high risk).

What is the latest version of dirty-memoize?

The latest version of dirty-memoize is 0.0.4, released 2011-01-26.

Does dirty-memoize have known vulnerabilities?

No known vulnerabilities on the latest version of dirty-memoize.

Is dirty-memoize deprecated?

No, dirty-memoize is actively maintained. Latest release: 0.0.4 (2011-01-26).

What are alternatives to dirty-memoize?

Popular alternatives to dirty-memoize in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does dirty-memoize use?

License information for dirty-memoize is not declared in the registry metadata.

dirty-memoize

rubygemsv0.0.4

Like Memoize, but designed for mutable and parametizable objects Use when: 1. You have one expensive method (\compute) which set many internal variables. So, is preferable lazy evaluation of these dependent variables. 2. The expensive operation depends on one or more parameters 3. Changes on one or more parameters affect all dependent variables 4. You may want to hide the call of 'compute' operation 5. The user could want test several different parameters values

3 versions0 deps655,864 weekly dl

http://github.com/clbustos/dirty-memoize

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

3/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/dirty-memoize