AI CODE DETECTOR GUIDE

Do Markdown code fences change an AI code detector result?

A pasted Markdown fence is scanned as part of the input; the current detector does not remove or parse the wrapper. In a tested example, the same code kept the same score, but its matched line moved down because the opening fence added a line.

The configured rules run in your browser; submitted code is not uploaded.

What happens to a fenced snippet

The paste flow passes the textarea's text to the analyzer, which splits it into lines and evaluates those lines. It does not first strip Markdown markers such as ```javascript. So a fenced snippet reaches analysis with the opening and closing fence lines still present.

For example, the source-only input is one line:

function calculateCustomerTotal() { return 1; }

With a Markdown wrapper, it is three input lines:

```javascript
function calculateCustomerTotal() { return 1; }
```

A direct test using the current rules matched the descriptive-identifier signal on line 1 for the source-only sample and line 2 for the fenced sample. Both tests returned the same score, 7. That is a result for these exact inputs and the current rule set—not a guarantee that adding arbitrary wrapper text never affects a heuristic score.

Which version should you paste?

For source-line references that map directly to your file, paste the code without Markdown fences. If you keep the fences, treat their lines as part of the submitted text when reading the report. The score and matched lines are heuristic signals, not proof of who wrote the code.

Open the AI code detector, or read how the report numbers lines.