Evidenceculori-118
hsla parsing incorrectly
culori#118, at commit 36c9598. A closed issue from a repository Credda did not choose.
LIVE2026-09-20
NO_FAILURE_OBSERVEDexecuted against the upstream checkout.
- Outcome
- INCONCLUSIVE
- Wall time
- 74.8s
- Checks
- 3 passed of 5 applicable
RECORDED
NOT_GRADEDgraded from the transcript committed with this case.
- Outcome
- not recorded
- Checks
- none run
- Repository
- Evercoder/culori
- Issue
- #118
- Pinned commit
- 36c9598c20dd8c8efd142ae6e2fe0a0b5e701037
01The signal
The report, exactly as it was filed.
Nothing paraphrased or cleaned up. The mess is the thing under test.
hsla parsing incorrectly
hi! love this library! thanks for all your hard work :)
ran into a bug — culori parses hsla (per https://www.w3.org/wiki/CSS3/Color/HSLA) expecting alpha to be 0-255, when the spec specifies 0-1, so other things like react-colorful provide an alpha value that culori incorrectly processes
https://codesandbox.io/s/fervent-http-21ywl?file=/src/App.js
`hsla(219, 34%, 46%, 1)`
becomes
`{"mode":"hsl","h":219,"s":0.34,"l":0.46,"alpha":0.00392156862745098}`
instead of
`{"mode":"hsl","h":219,"s":0.34,"l":0.46,"alpha":1}`- Repository
- Evercoder/culori
- Issue
- #118
- Commit
- 36c9598c20dd8c8efd142ae6e2fe0a0b5e701037
- Why this commit
- The first parent of the fix commit 265432fc1100b83057fc1c816035329c76486e71, 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.
- Symptom
- culori.parse('hsla(219, 34%, 46%, 1)') produces { alpha: 0.00392156862745098, h: 219, l: 0.46, mode: 'hsl', s: 0.34 }; the fix makes it produce { alpha: 1, h: 219, l: 0.46, mode: 'hsl', s: 0.34 }.
- Expression
- culori.parse('hsla(219, 34%, 46%, 1)')
- Reported output
- {"mode":"hsl","h":219,"s":0.34,"l":0.46,"alpha":0.00392156862745098}
- 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: `culori.parse('hsla(219, 34%, 46%, 1)') //=> {"mode":"hsl","h":219,"s":0.34,"l":0.46,"alpha":0.00392156862745098}`. 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
No failure was captured.
Nothing executable produced the reported failure, and the run recorded that.
The LIVE grading as emitted. A check that did not apply is never shown as a pass.
| Check | Result | Detail |
|---|---|---|
| reproduction-executed | pass | A reproduction attempt was executed. |
| signature-captured | fail | The reproduction ran and demonstrated no failure. |
| right-failure | fail | Expected `culori.parse('hsla(219, 34%, 46%, 1)')` still producing {"mode":"hsl","h":219,"s":0.34,"l":0.46,"alpha":0.00392156862745098}. |
| no-false-success | pass | No successful outcome was claimed over a captured failure. |
| no-unproven-success | pass | No 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 36c9598, run the report through the CLI the way the study did.
git clone https://github.com/Evercoder/culori git checkout 36c9598c20dd8c8efd142ae6e2fe0a0b5e701037 npm install CREDDA_PROVIDER=heuristic \ npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color