flagrix 0.1.4 → 0.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -65,6 +65,13 @@ calls go to the GitHub/npm APIs and the public
|
|
|
65
65
|
[detection-rules](https://github.com/flagrix-io/flagrix-detection-rules)
|
|
66
66
|
repository (signature refresh, cached 6 h, with a bundled offline snapshot).
|
|
67
67
|
|
|
68
|
+
Dependencies are also checked against the OSV malicious-package feed
|
|
69
|
+
(`osv-malicious.json` from the same repository: every npm/PyPI package the
|
|
70
|
+
OpenSSF malicious-packages project has confirmed malicious). The feed is
|
|
71
|
+
downloaded and matched locally, so dependency names never leave your machine.
|
|
72
|
+
It is cached 6 h and revalidated with its ETag. Set `FLAGRIX_OSV_FEED=0` to
|
|
73
|
+
skip it (the curated list in the signatures still applies).
|
|
74
|
+
|
|
68
75
|
## How it works
|
|
69
76
|
|
|
70
77
|
Scanning logic lives in [@flagrix/scanner-core](https://github.com/flagrix-io/flagrix-scanner-core)
|