@@ -7,8 +7,8 @@ When analyzing a Go program, CodeQL does not examine the source code for
7
7
external packages. To track the flow of untrusted data through a library, you
8
8
can create a model of the library.
9
9
10
- You can find existing models in the ``ql/src /semmle/go/frameworks/ `` folder of the
11
- `CodeQL for Go repository <https://github.com/github/codeql-go/tree/main/ql/src /semmle/go/frameworks >`__.
10
+ You can find existing models in the ``ql/lib /semmle/go/frameworks/ `` folder of the
11
+ `CodeQL for Go repository <https://github.com/github/codeql-go/tree/main/ql/lib /semmle/go/frameworks >`__.
12
12
To add a new model, you should make a new file in that folder, named after the library.
13
13
14
14
Sources
@@ -102,8 +102,8 @@ Data-flow sinks are specified by queries rather than by library models.
102
102
However, you can use library models to indicate when functions belong to
103
103
special categories. Queries can then use these categories when specifying
104
104
sinks. Classes representing these special categories are contained in
105
- ``ql/src /semmle/go/Concepts.qll `` in the `CodeQL for Go repository
106
- <https://github.com/github/codeql-go/blob/main/ql/src /semmle/go/Concepts.qll> `__.
105
+ ``ql/lib /semmle/go/Concepts.qll `` in the `CodeQL for Go repository
106
+ <https://github.com/github/codeql-go/blob/main/ql/lib /semmle/go/Concepts.qll> `__.
107
107
``Concepts.qll `` includes classes for logger mechanisms,
108
108
HTTP response writers, HTTP redirects, and marshaling and unmarshaling
109
109
functions.
0 commit comments