Recordsnpmasync-exit-hook2.0.1
Change the conditions
Current conditions
async-exit-hook @2.0.1windows 11 · x64 · node 22 · npm 11 · node
package-level total, not an API
14 of 15 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (5)
- Project observations
- 14 / 15
- Contract verifications
- nothing at this coordinate
- Usage records
- 5
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 1
- Last recorded
- 2026-08-24
Evidence you can open
Dependency Health
A resolution read this release's tree and found no dependencies. That is a measurement, not a missing one.
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×6 2.0.1 executionContext=node · moduleSystem=cjs sha256:bc4d7ddc5bcd…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>npm · unclassified-diagnostic · outer npm run, npm test · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-09-02 · Last seen: 2026-09-14Diagnostic re-verification candidate
-
observed PROJECT_TEST Evidence gap ×5 2.0.1 executionContext=node · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-21 · Last seen: 2026-08-25Diagnostic re-verification candidate
-
observed PROJECT_TYPECHECK Evidence gap ×2 2.0.1 executionContext=node · moduleSystem=cjs · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-19 · Last seen: 2026-08-21Diagnostic re-verification candidate