Records/npm/std-env/failure issue

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.0 FAIL
• 3.10.0 not measured

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×2 2026-09-13 → 2026-09-13

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

• std-env 4.2.0: runtimeInfo Built ? 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. HOWstd-env.runtimeInfo MIT-0 · 2026-09-17
• std-env 4.2.0: providerInfo Built ? 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. HOWstd-env.providerInfo MIT-0 · 2026-09-17
• std-env 4.2.0: provider Built ? 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. HOWstd-env.provider MIT-0 · 2026-09-17