Recordsnpmreal-requirefailure issue
Failure signature
UNKNOWN exit 1 ELSPROBLEMS Evidence gap ×1
npm error code ELSPROBLEMS · npm error missing: real-require@0.2.0, required by isolated-real-require-check@1.0.0 …
Evidence quality: complete · npm · unclassified-diagnostic · outer npm · gap stage-unknown · First recorded: 2026-09-14 · Last seen: 2026-09-14
sha256:92c0609279ba…
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.
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-09-14 → 2026-09-14
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: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- real-require 0.2.0: verify realRequire from 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. HOWrealRequirenode 22.23.2 MIT-0 · 2026-08-21