Is cohort_analysis safe to use?

cohort_analysis has no known vulnerabilities on the latest version (1.0.3). DepScope rates its health at 34/100 (critical risk).

What is the latest version of cohort_analysis?

The latest version of cohort_analysis is 1.0.3, released 2012-06-06.

Does cohort_analysis have known vulnerabilities?

No known vulnerabilities on the latest version of cohort_analysis.

Is cohort_analysis deprecated?

No, cohort_analysis is actively maintained. Latest release: 1.0.3 (2012-06-06).

What are alternatives to cohort_analysis?

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

What license does cohort_analysis use?

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

cohort_analysis

rubygemsv1.0.3

Lets you do cohort analysis based on two strategies: "big", which discards characteristics for the maximum cohort result, and "strict", which discards characteristics in order until a minimum cohort size is reached.

5 versions2 deps9,198 weekly dl

seamusabshere/cohort_analysis

/ 100

Health

use with caution

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

Low health score (34/100)

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

activesupport arel

API access

Get this data programmatically — free, no authentication.

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