Recordsnpmhonofailure issue
Failure signature
PROJECT_RESOLVE exit 1 ERESOLVE ×1
npm error code ERESOLVE
Evidence quality: complete · node/npm · resolve-diagnostic · outer npm install · First recorded: 2026-09-02 · Last seen: 2026-09-02
sha256:3c31643e02d8…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 4.13.5 not measured
- 4.13.3 not measured
- 4.13.2 not measured
- 4.13.1 FAIL
- 4.12.32 not measured
- 4.6.0 not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-09-02 → 2026-09-02
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
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 5
- No failure domain was inferred for this failure.
Published answers for the affected releases
- hono 4.13.1: bearerAuth 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. HOWhono.bearerAuthnode 22.23.2 MIT-0 · 2026-09-06
- hono 4.13.1: bearerAuth 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. HOWbearerAuth MIT-0 · 2026-09-01
- hono 4.13.1: bearer-auth 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. HOWhono/bearer-authnode 22.23.2 MIT-0 · 2026-09-01