Recordsnpmproper-lockfile4.1.2
Change the conditions
Current conditions
proper-lockfile @4.1.2windows 11 · x64 · node 22 · pnpm 10 · node
package-level total, not an API
11 of 14 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 (4)
- Project observations
- 11 / 14
- Contract verifications
- nothing at this coordinate
- Usage records
- 72
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 3
- Last recorded
- 2026-08-23
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Steady 3
First observed break
4.1.2
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| graceful-fs | 4.2.11 | PASS All observations passed | contract passed | 20 project-days |
| retry | 0.12.0 | PASS All observations passed | contract passed | 19 project-days |
| signal-exit | 3.0.7 | PASS All observations passed | contract passed | 20 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Recent failure clusters
-
observed PROJECT_TEST Evidence gap ×4 4.1.2 executionContext=node · moduleSystem=esm · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-23 · Last seen: 2026-08-25Diagnostic re-verification candidate
-
observed PROJECT_TYPECHECK Evidence gap ×1 4.1.2 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@22.16Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-20 · Last seen: 2026-08-20