Recordsnpmfast-urifailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×2
<anonymous_script>:<n> · const Serializer = require(<str>) · ^ · ReferenceError: require is not defined in ES module scope, you can use import instead
Evidence quality: complete · npm · unclassified-diagnostic · outer npm test · gap stage-unknown · First recorded: 2026-10-19 · Last seen: 2026-10-19
sha256:1a0c0f86bf99…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 4.2.3 not measured
- 4.2.2 FAIL
- 4.1.2 not measured
- 3.1.9 not measured
- 3.1.8 FAIL
- 3.1.6 not measured
- 3.1.5 not measured
- 3.1.4 not measured
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×2 2026-10-19 → 2026-10-19
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
- fast-uri 4.2.2 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. HOW MIT-0 · 2026-10-19