@@ -14,6 +14,10 @@ added as external data), and are picked up by the standard security queries, all
1414about flow into, out of and through the npm packages as though they had been included as part of the
1515build.
1616
17+ Note that flow summaries are an experimental technology, and not ready to be used in production
18+ queries or libraries. Also note that flow summaries do not currently work with CodeQL, but require
19+ the legacy Semmle Core toolchain.
20+
1721Motivating example
1822------------------
1923
@@ -87,11 +91,11 @@ package. (Note that this requires a working installation of Semmle Core.)
8791There are three default summary extraction queries:
8892
8993- Extract flow step summaries (``js/step-summary-extraction ``,
90- ``Security /Summaries/ExtractSourceSummaries.ql ``)
94+ ``experimental /Summaries/ExtractSourceSummaries.ql ``)
9195- Extract sink summaries (``js/sink-summary-extraction ``,
92- ``Security /Summaries/ExtractSinkSummaries.ql ``)
96+ ``experimental /Summaries/ExtractSinkSummaries.ql ``)
9397- Extract source summaries (``js/source-summary-extraction ``,
94- ``Security /Summaries/ExtractSourceSummaries.ql ``)
98+ ``experimental /Summaries/ExtractSourceSummaries.ql ``)
9599
96100You can run these queries individually against a snapshot of the npm package you want to create
97101flow summaries for using ``odasa runQuery ``, and store the output as CSV files named
@@ -103,7 +107,7 @@ project, we can extract sink summaries using the command
103107.. code-block :: bash
104108
105109 odasa runQuery \
106- --query $SEMMLE_DIST /queries/semmlecode-javascript-queries/Security /Summaries/ExtractSinkSummaries.ql \
110+ --query $SEMMLE_DIST /queries/semmlecode-javascript-queries/experimental /Summaries/ExtractSinkSummaries.ql \
107111 --output-file additional-sinks.csv --snapshot mkdirp-snapshot
108112
109113
0 commit comments