Sign in

Evidenceslugify-17

Run custom replacements before anything else

slugify#17, at commit 125fe7f. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
PATCH_REJECTED
Wall time
117.4s
Checks
5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
sindresorhus/slugify
Issue
#17
Pinned commit
125fe7fb3dfee1ad44fec75bca2529d14921ee27

01The signal

The report, exactly as it was filed.

Nothing paraphrased or cleaned up. The mess is the thing under test.

slugify#17 · as filedcommit 125fe7f

Run custom replacements before anything else

**What I expected:**

```
slugify('Zürich', {
      customReplacements: [["ä", "ae"], ["ö", "oe"], ["ü", "ue"], ["ß", "ss"]]
    })

// -> result: zuerich
```

**What I got instead:**

```
// -> result: zurich
```

**Reason:**

```
string = deburr(string);  <- will replace ü with u
string = decamelize(string);
string = doCustomReplacements(string, customReplacements);
```

**Possible solution:**

Run doCustomReplacements first.

```
string = doCustomReplacements(string, customReplacements);
string = deburr(string);
string = decamelize(string);
```

What do you think?
Issue
#17
Commit
125fe7fb3dfee1ad44fec75bca2529d14921ee27
Why this commit
The first parent of the fix commit 1edd6559d14eeebf86d315c7ff983df85131e4b6, which GitHub binds to this issue via CLOSED_EVENT_COMMIT. Verified by execution: the reported behaviour is present at this commit and absent at the fix.
How the text was obtained
Fetched verbatim via the GitHub GraphQL API. Title on the first line, body unmodified below it. Nothing was paraphrased, cleaned up, or supplemented.
Toolchain
javascript · node · unknown · npm

02What counts as reproducing it

The bar, written down before the run.

expected.reportedFailurecommitted with the case
Symptom
slugify('Zürich', {customReplacements: [["ä", "ae"], ["ö", "oe"], ["ü", "ue"], ["ß", "ss"]]}) does not produce "zuerich"; the fix makes it do so.
Expression
slugify('Zürich', {customReplacements: [["ä", "ae"], ["ö", "oe"], ["ü", "ue"], ["ß", "ss"]]})
Where that came from
Proposed by a model reading this report and nothing else -- it never saw the repository or the fix commit -- and read back as a claim by the same parser the harvest uses, SAME_LINE form: `slugify('Zürich', {customReplacements: [["ä", "ae"], ["ö", "oe"], ["ü", "ue"], ["ß", "ss"]]}) //=> "zuerich"`. The report sat in the ANNOTATION_IS_PROSE bucket, which no regex reaches. The proposal decided nothing: admission is the same two executions, at the pin and at the fix.

03What happened

The live run reproduced the reported failure.

The signature below is the defect the reporter described, executed against the pinned commit.

captured failure signatureLIVE · normalized
`slugify('Zürich', {
customReplacements: [["ä", "ae"], ["ö", "oe"], ["ü", "ue"], ["ß", "ss"]]
})` still produces zuerich (read zurich)
bench external · checks · LIVE5 checks · 2026-09-20

The LIVE grading as emitted. A check that did not apply is never shown as a pass.

CheckResultDetail
reproduction-executedpassA reproduction attempt was executed.
signature-capturedpass`slugify('Zürich', { customReplacements: [["ä", "ae"], ["ö", "oe"], ["ü", "ue"], ["ß", "ss"]] })` still produces zuerich (read zurich)
right-failurepassReproduced the reported failure: slugify('Zürich', {customReplacements: [["ä", "ae"], ["ö", "oe"], ["ü", "ue"], ["ß", "ss"]]}) does not produce "zuerich"; the fix makes it do so.
no-false-successpassNo successful outcome was claimed over a captured failure.
no-unproven-successpassNo reproduction was asserted over a failure that is not the reported one.

bench/external/scorecard.json, the run of 2026-09-20 against all 158 upstream checkouts.

The same case, graded from the transcript recorded .

The grading the benchmark gate runs on. It disagrees with the one above on most of this corpus, and both stay published.

Check it yourself

Everything here is downstream of a public commit.

Clone it, check out 125fe7f, run the report through the CLI the way the study did.

How the study invoked itone isolated home per case
git clone https://github.com/sindresorhus/slugify
git checkout 125fe7fb3dfee1ad44fec75bca2529d14921ee27
npm install

CREDDA_PROVIDER=heuristic \
  npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color
Read the full studyAll 158 cases