Records/npm/commander/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 10.0.1 not measured
• 10.0.0 not measured
• 9.5.0 PASS 185 passing observations
• 7.2.0 FAIL
• 5.1.0 PASS 193 passing observations
• 4.1.1 FAIL
• 2.20.3 FAIL

Where it reproduced

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

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 4.1.1 → first passing release 5.1.0

  Both trees resolved every dependency to the same version. Nothing here moved.

• Last passing release 5.1.0 → first failing release 7.2.0

  Both trees resolved every dependency to the same version. Nothing here moved.

• Last failing release 7.2.0 → first passing release 9.5.0

  Both trees resolved every dependency to the same version. Nothing here moved.

Evidence gaps

• Releases in this window never measured at PROJECT_COMPILE: 2
• No failure domain was inferred for this failure.

Published answers for the affected releases

• commander 4.1.1 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. HOWnode 22.23.2 MIT-0 · 2026-08-20
• commander 2.20.3: Parse options, custom coercion, and command arguments in commander 2.20.3 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. HOWCommand.actionCommand.optionCommand.parse MIT-0 · 2026-08-27