GraphQL is a query language and execution engine tied to any backend service.
This report summarizes scanner evidence for graphql/graphql-spec, a HTML project with 14,591 GitHub stars. SynthScan examined 43,217 lines of code across 44 source files, recording 51 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 6.0 (Moderate pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Can maintainers explain intent, assumptions, and trade-offs? 51 finding(s).
Are imports declared and package/API names verified? 0 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 51 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 51 distinct pattern matches across 2 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | published/June2018/index.html | 854 | </code></pre></section><section id="sec-Language.Arguments" secid="2.6"><h3><span class="spec-secid" title="link to this | CODE |
| HIGH | published/June2018/index.html | 874 | </code></pre></section><section id="sec-Field-Alias" secid="2.7"><h3><span class="spec-secid" title="link to this sectio | CODE |
| HIGH | published/June2018/index.html | 952 | </code></pre><p>The queries <code>noFragments</code>, <code>withFragments</code>, and <code>withNestedFragments</code> a | CODE |
| HIGH | published/June2018/index.html | 1037 | </code></pre><p><strong>Semantics</strong></p><div class="spec-semantic"><span class="spec-nt"><a href="#ObjectValue" da | CODE |
| HIGH | published/June2018/index.html | 1214 | </code></pre></section><section id="sec-Object-Extensions" secid="3.6.3"><h4><span class="spec-secid" title="link to thi | CODE |
| HIGH | published/June2018/index.html | 1263 | </code></pre><p><strong>Result Coercion</strong></p><p>The interface type should have some way of determining which obje | CODE |
| HIGH⚡ | published/June2018/index.html | 1309 | </code></pre><p><strong>Result Coercion</strong></p><p>The union type should have some way of determining which object a | CODE |
| HIGH⚡ | published/June2018/index.html | 1315 | </code></pre><p><strong>Result Coercion</strong></p><p>GraphQL servers must return one of the defined set of possible va | CODE |
| HIGH⚡ | published/June2018/index.html | 1332 | </code></pre><div class="spec-note">The Validation section defines providing a nullable variable type to a non‐nul | CODE |
| HIGH | published/October2015/index.html | 818 | </code></pre></section><section id="sec-Language.Query-Document.Arguments" secid="2.2.4"><h4><span class="spec-secid" ti | CODE |
| HIGH | published/October2015/index.html | 838 | </code></pre></section><section id="sec-Field-Alias" secid="2.2.5"><h4><span class="spec-secid" title="link to this sect | CODE |
| HIGH | published/October2015/index.html | 916 | </code></pre><p>The queries <code>noFragments</code>, <code>withFragments</code>, and <code>withNestedFragments</code> a | CODE |
| HIGH | published/October2015/index.html | 973 | </code></pre></section></section><section id="sec-Input-Values" secid="2.2.7"><h4><span class="spec-secid" title="link t | CODE |
| HIGH⚡ | published/October2015/index.html | 1138 | </code></pre><p>Hence, if the value for a Non Null type is hard‐coded in the query, it is always coerced using the | CODE |
| HIGH⚡ | published/October2015/index.html | 1141 | </code></pre></section><section id="sec--include" secid="3.2.2"><h4><span class="spec-secid" title="link to this section | CODE |
| HIGH | published/April2016/index.html | 818 | </code></pre></section><section id="sec-Language.Arguments" secid="2.6"><h3><span class="spec-secid" title="link to this | CODE |
| HIGH | published/April2016/index.html | 838 | </code></pre></section><section id="sec-Field-Alias" secid="2.7"><h3><span class="spec-secid" title="link to this sectio | CODE |
| HIGH | published/April2016/index.html | 916 | </code></pre><p>The queries <code>noFragments</code>, <code>withFragments</code>, and <code>withNestedFragments</code> a | CODE |
| HIGH | published/April2016/index.html | 979 | </code></pre><p><strong>Semantics</strong></p><div class="spec-semantic"><span class="spec-nt"><a href="#ObjectValue">Ob | CODE |
| HIGH⚡ | published/April2016/index.html | 1173 | </code></pre></section></section><section id="sec-Type-System.Directives" secid="3.2"><h3><span class="spec-secid" title | CODE |
| HIGH⚡ | published/April2016/index.html | 1176 | </code></pre></section><section id="sec--include" secid="3.2.2"><h4><span class="spec-secid" title="link to this section | CODE |
| HIGH | published/October2021/index.html | 658 | <p data-source="spec/Section%202%20--%20Language.md#L418-L419">In this example, we want to query a specific user (reques | CODE |
| HIGH | published/October2021/index.html | 696 | <p data-source="spec/Section%202%20--%20Language.md#L470-L471">In this example, we can fetch two profile pictures of dif | CODE |
| HIGH | published/October2021/index.html | 809 | <p data-source="spec/Section%202%20--%20Language.md#L615-L616">Fragments must specify the type they apply to. In this ex | CODE |
| HIGH | published/October2021/index.html | 1301 | <p data-source="spec/Section%202%20--%20Language.md#L1112-L1113">In this example, we want to fetch a profile picture siz | CODE |
| HIGH | published/October2021/index.html | 1520 | <p data-source="spec/Section%203%20--%20Type%20System.md#L193-L194">In this example, a GraphQL schema is defined with bo | CODE |
| HIGH | published/October2021/index.html | 2033 | <p data-source="spec/Section%203%20--%20Type%20System.md#L1008">In this example, a local data field is added to a <code> | CODE |
| HIGH | published/October2021/index.html | 2039 | <p data-source="spec/Section%203%20--%20Type%20System.md#L1019">In this example, a directive is added to a <code>User</c | CODE |
| HIGH | published/October2021/index.html | 2201 | <p data-source="spec/Section%203%20--%20Type%20System.md#L1244-L1245">In this example, an extended data field is added t | CODE |
| HIGH | published/October2021/index.html | 2215 | <p data-source="spec/Section%203%20--%20Type%20System.md#L1264-L1265">In this example, a directive is added to a <code>N | CODE |
| HIGH | published/October2021/index.html | 2260 | <p data-source="spec/Section%203%20--%20Type%20System.md#L1329-L1331">In this example, a query operation wants the name | CODE |
| HIGH | published/October2021/index.html | 2335 | <p data-source="spec/Section%203%20--%20Type%20System.md#L1427">In this example, an Enum type called <code>Direction</co | CODE |
| HIGH | published/October2021/index.html | 2389 | <p data-source="spec/Section%203%20--%20Type%20System.md#L1499">In this example, an Input Object called <code>Point2D</c | CODE |
| HIGH | published/October2021/index.html | 2864 | <p data-source="spec/Section%203%20--%20Type%20System.md#L1913-L1914">Directives must only be used in the locations they | CODE |
| HIGH | published/October2021/index.html | 2878 | <p data-source="spec/Section%203%20--%20Type%20System.md#L1939">In this example, the directive <code>@example</code> ann | CODE |
| HIGH | published/October2021/index.html | 2919 | <p data-source="spec/Section%203%20--%20Type%20System.md#L1999-L2000">In this example <code>experimentalField</code> wil | CODE |
| HIGH | published/October2021/index.html | 2930 | <p data-source="spec/Section%203%20--%20Type%20System.md#L2019-L2020">In this example <code>experimentalField</code> wil | CODE |
| HIGH | published/October2021/index.html | 2947 | <p data-source="spec/Section%203%20--%20Type%20System.md#L2051-L2052">In this example type definition, <code>oldField</c | CODE |
| HIGH | published/October2021/index.html | 2959 | <p data-source="spec/Section%203%20--%20Type%20System.md#L2074-L2075">In this example, a custom scalar type for <code>UU | CODE |
| HIGH | published/October2021/index.html | 3815 | <p data-source="spec/Section%205%20--%20Validation.md#L553-L555">However, the field responses must be shapes which can b | CODE |
| HIGH | published/October2016/index.html | 818 | </code></pre></section><section id="sec-Language.Arguments" secid="2.6"><h3><span class="spec-secid" title="link to this | CODE |
| HIGH | published/October2016/index.html | 838 | </code></pre></section><section id="sec-Field-Alias" secid="2.7"><h3><span class="spec-secid" title="link to this sectio | CODE |
| HIGH | published/October2016/index.html | 916 | </code></pre><p>The queries <code>noFragments</code>, <code>withFragments</code>, and <code>withNestedFragments</code> a | CODE |
| HIGH | published/October2016/index.html | 983 | </code></pre><p><strong>Semantics</strong></p><div class="spec-semantic"><span class="spec-nt"><a href="#ObjectValue">Ob | CODE |
| HIGH⚡ | published/October2016/index.html | 1181 | </code></pre><div class="spec-note">The Validation section defines providing a nullable variable type to a non‐nul | CODE |
| HIGH⚡ | published/October2016/index.html | 1184 | </code></pre></section><section id="sec--include" secid="3.2.2"><h4><span class="spec-secid" title="link to this section | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | published/June2018/index.html | 1323 | </code></pre><table><thead><tr><th>Literal Value </th><th>Variables </th><th>Coerced Value</th></tr></thead><tbody><tr>< | CODE |
| LOW⚡ | published/October2015/index.html | 1129 | </code></pre><p><strong>Result Coercion</strong></p><p>The union type should have some way of determining which object a | CODE |
| LOW⚡ | published/April2016/index.html | 1164 | </code></pre><p><strong>Result Coercion</strong></p><p>The union type should have some way of determining which object a | CODE |
| LOW | published/October2021/index.html | 2592 | <p data-source="spec/Section%203%20--%20Type%20System.md#L1711-L1714">This allows inputs which accept one or many argume | CODE |
| LOW⚡ | published/October2016/index.html | 1172 | </code></pre><table><thead><tr><th>Original Value </th><th>Variables </th><th>Coerced Value</th></tr></thead><tbody><tr> | CODE |