Sign in

Evidenceslugify-9

Custom replacements don't work as expected

slugify#9, at commit 96ddd5f. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
PARTIALLY_VERIFIED
Wall time
104.0s
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
#9
Pinned commit
96ddd5fd5bfc80f5f902cc9bd0b24cb61e9c279f

01The signal

The report, exactly as it was filed.

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

slugify#9 · as filedcommit 96ddd5f

Custom replacements don't work as expected

... Or at least don't work as I would expect them to work :)

Example:

``` javascript
import slugify from '@sindresorhus/slugify';

const customSlugify = string => slugify(string, {
  customReplacements: [
    ['.', ''],
  ],
});

const slugified = customSlugify('x.y.z'); // Expected `xyz`, received `x-y-z`
```

I expected all dots to be converted into empty strings, so the expected result was `xyz` but I received `x-y-z`

---
I suppose that it's not a bug, but it would be good if the documentation explained how custom replacements really work.
Issue
#9
Commit
96ddd5fd5bfc80f5f902cc9bd0b24cb61e9c279f
Why this commit
The first parent of the fix commit 296fbd51ad808cc378032a3631025a55541772bb, which GitHub binds to this issue via CLOSED_EVENT_PR. 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('x.y.z', { customReplacements: [['.','']] }) produces 'x-y-z'; the fix makes it produce 'xyz'.
Expression
slugify('x.y.z', { customReplacements: [['.','']] })
Reported output
"x-y-z"
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('x.y.z', { customReplacements: [['.','']] }) //=> "x-y-z"`. The report sat in the NO_FENCE_INLINE_CODE_ONLY 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
`customSlugify('x.y.z')` still produces "x-y-z" (read x-y-z)
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`customSlugify('x.y.z')` still produces "x-y-z" (read x-y-z)
right-failurepassReproduced the reported failure: slugify('x.y.z', { customReplacements: [['.','']] }) produces 'x-y-z'; the fix makes it produce 'xyz'.
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 96ddd5f, 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 96ddd5fd5bfc80f5f902cc9bd0b24cb61e9c279f
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