Recordsnpmcontent-typefailure issue
Failure signature
PROJECT_TEST exit 1 ERR_ASSERTION ×2
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · undefined !== 123 · at <url> …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-10-21 · Last seen: 2026-10-21
sha256:ef96efaca8dd…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×2 2026-10-21 → 2026-10-21
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release 1.0.5 → first passing release 2.0.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release 2.0.0 → first failing release 2.1.0
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- content-type 2.1.0: contentType.format, contentType.parse This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcontentType.formatcontentType.parse MIT-0 · 2026-08-18
- content-type 1.0.5: parse and format HTTP Content-Type header with parameters This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcontentType.formatcontentType.parse MIT-0 · 2026-08-18