From 05acd81f4a76f564b8f48ddfbe84f9142dda51de Mon Sep 17 00:00:00 2001 From: Helge Date: Fri, 19 Mar 2021 15:02:03 +0100 Subject: [PATCH] Fixed link to image --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 64490a6..090e697 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ This project was triggered by the [announcement](https://opensource.googleblog.c Pike describes a generic formula for computing criticality of a package as a normalized weighed sum of the ratio of the logarithm of signal[s (Si)], the logarithm of the maximum of signal value and a corresponding threshold Ti: -https://raw.githubusercontent.com/ossf/criticality_score/main/images/formula.png +![](https://raw.githubusercontent.com/ossf/criticality_score/main/images/formula.png) In [his paper](https://github.com/ossf/criticality_score/blob/a02c8311fbbbd5d569ebaad3106ec08532b3a10c/Quantifying_criticality_algorithm.pdf), Pike mentions as possible signals the number of package downloads or the number of its dependents. He does not provide any weights or thresholds. However, the [current implementation of the criticality score](https://github.com/ossf/criticality_score/blob/4a3e3e171ac403344060dbcfc43f47944afe77d0/criticality_score/run.py) relies on ten signals, such as, time since creation in months, time since latest update in months, average number of comments per issue over the last 90 days, etc. together with corresponding weights and thresholds.