Sign in

EvidenceTinyColor-36

rgb range 0-1 not correctly recognized

TinyColor#36, at commit 20f7929. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

NO_FAILURE_OBSERVED

executed against the upstream checkout.

Outcome
NO_CHANGE_REQUIRED
Wall time
53.2s
Checks
3 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
bgrins/TinyColor
Issue
#36
Pinned commit
20f7929951916b1648c73941ab7e4215da6e1a8f

01The signal

The report, exactly as it was filed.

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

TinyColor#36 · as filedcommit 20f7929

rgb range 0-1 not correctly recognized

I would expect it to recognize a range of [0-1] if all numbers are decimal and bound to 0-1, as in older version (this result is from v0.5):

``` javascript
tinycolor('rgb(0.9, 0.0, 0.0)').toRgbString()
"rgb(230, 0, 0)"
```

But it now seems to only work when there's a 1.0 somewhere (at least after 0.9.14): 

``` javascript
tinycolor('rgb(0.9, 0.0, 0.0)').toRgbString()
"rgb(1, 0, 0)"
tinycolor('rgb(1.0, 0.0, 0.0)').toRgbString()
"rgb(255, 0, 0)"
```

Am I doing it wrong? Should I try to fix it?
Issue
#36
Commit
20f7929951916b1648c73941ab7e4215da6e1a8f
Why this commit
The first parent of the fix commit a1cb0deb8fc35248fa0153d9bd064bb23d2ee56e, which GitHub binds to this issue via REFERENCED_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
tinycolor('rgb(0.9, 0.0, 0.0)').toRgbString() produces 'rgb(1, 0, 0)'; the fix makes it produce 'rgb(230, 0, 0)'.
Expression
tinycolor('rgb(0.9, 0.0, 0.0)').toRgbString()
Reported output
"rgb(1, 0, 0)"
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: `tinycolor('rgb(0.9, 0.0, 0.0)').toRgbString() //=> "rgb(1, 0, 0)"`. The report sat in the CODE_NO_ANNOTATION_AT_ALL 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.

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-capturedfailThe reproduction ran and demonstrated no failure.
right-failurefailExpected `tinycolor('rgb(0.9, 0.0, 0.0)').toRgbString()` still producing "rgb(1, 0, 0)".
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 20f7929, 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/bgrins/TinyColor
git checkout 20f7929951916b1648c73941ab7e4215da6e1a8f
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