Recordsnpmcontent-typefailure issue
Failure signature
PROJECT_TEST exit 1 ERR_ASSERTION ×1
AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal: · + actual - expected · Comparison { · + message: <str>,
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-10-18 · Last seen: 2026-10-18
sha256:8c3539be02dd…
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.
- 3.1.0 not measured
- 3.0.0 not measured
- 2.1.0 FAIL
- 2.0.0 PASS 186 passing observations
- 1.0.5 PASS 198 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×1 2026-10-18 → 2026-10-18
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 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