Evidencepathe-18

`dirname` of non-absolute filename returns `/`

pathe#18, at commit 69696c4. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

NOT_EXECUTED

executed against the upstream checkout.

Outcome
ERRORED
Wall time
212.8s
Checks
2 passed of 4 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
unjs/pathe
Issue
#18
Pinned commit
69696c48003ae457e018c31edf41981b06c41d34

01The signal

The report, exactly as it was filed.

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

pathe#18 · as filedcommit 69696c4

`dirname` of non-absolute filename returns `/`

```js
dirname('test.mjs')
// prints '/'
// should be '.'
```
Repository
unjs/pathe
Issue
#18
Commit
69696c48003ae457e018c31edf41981b06c41d34
Why this commit
The first parent of the fix commit e15d5da0efba221209190deb2f3f98466f135d78, 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
dirname('test.mjs') produces '/'; the fix makes it produce '.'.
Expression
dirname('test.mjs')
Reported output
'/'
Where that came from
Read mechanically from the report's fenced code, NEXT_LINE form: `dirname('test.mjs') // prints '/'`.

03What happened

No failure was captured.

Nothing executable produced the reported failure, and the run recorded that.

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.

Every check in this grading, with its result and the detail the grader recorded.
CheckResultDetail
reproduction-executedfailNothing ran: the environment never came up (Failed to prepare the sandbox environment: DEPENDENCY_INSTALL_FAILED). This is not an extraction result -- the report was never reached.
signature-capturedn/aThe reproduction ran and demonstrated no failure.
right-failurefailExpected `dirname('test.mjs')` still producing '/'.
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 69696c4, 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/unjs/pathe
git checkout 69696c48003ae457e018c31edf41981b06c41d34
npm install

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