Recordsnpmvalidate-npm-package-namefailure issue
Failure signature
PROJECT_TEST exit 1 ERR_ASSERTION ×1
AssertionError [ERR_ASSERTION]: Missing expected exception. · at <url> · at ModuleJob.run (node:internal/modules/esm/module_job:<n>:<n>) …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-10-17 · Last seen: 2026-10-17
sha256:2c4eb57fcc76…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST 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=esm · os=linux · runtime=node@22.23 ×1 2026-10-17 → 2026-10-17
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 6.0.2 → first passing release 7.0.2
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- validate-npm-package-name 6.0.2: validate 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. HOWvalidate MIT-0 · 2026-10-18
- validate-npm-package-name 6.0.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-17