Recordsnpmown-keys1.0.1
Change the conditions
Current conditions
own-keys @1.0.1windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
0 of 9 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 20 / 68
- Contract verifications
- 0 / 9
- Usage records
- 46
- Independent reporting peers
- 1
- Last recorded
- 2026-09-16
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Steady 3
First observed break
1.0.1
windows · node@24.13 · moduleSystem=cjs · executionContext=node
4 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| get-intrinsic | 1.3.0 | PASS All observations passed | contract passed | 3 project-days |
| object-keys | 1.1.1 | PASS All observations passed | contract passed | 3 project-days |
| safe-push-apply | 1.0.0 | PASS All observations passed | contract passed | 3 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.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 1.0.2 | 1.0.1 |
|---|---|---|
| call-bound | 1.0.4 | — |
| get-intrinsic | 1.3.0 | 1.3.0 |
| object-keys | 1.1.1 | 1.1.1 |
| safe-push-apply | 1.0.0 | 1.0.0 |
Moved: 0 · unchanged at every release: 4
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Recent failure clusters
-
observed PROJECT_COMPILE exit 2 TS2307 ×4 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:0470f88d95bb…lib/hooks/queries/index.ts(<n>,<n>): error TS2307: Cannot find module <str> or its corresponding type declarations. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS7006 ×4 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:21025cd78572…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS7006: Parameter <str> implicitly has an <str> type. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2561 ×4 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:5f96e966539e…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2561: Object literal may only specify known properties, but <str> does not exist in type …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2345 ×4 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:7e077f646acc…lib/api/real-estate-statistics.ts(<n>,<n>): error TS2345: Argument of type <str> is not assignable to parameter of type <str>.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2551 ×4 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:8a1ebc675f2b…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2551: Property <str> does not exist on type <str>. Did you mean <str>? …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2339 ×4 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:e51205820175…lib/api/real-estate-map-addresses.ts(<n>,<n>): error TS2339: Property <str> does not exist on type <str>.typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2305 ×4 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:e7aa54217e13…app/api/politicians/[id]/real-estates/route.ts(<n>,<n>): error TS2305: Module <str> has no exported member <str>. …typescript/tsc · compiler-diagnosticEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2345 ×2 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:0d787687eb6d…lib/services/sync-service.ts(<n>,<n>): error TS2345: Argument of type <str> is not assignable to parameter of type <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2322 ×2 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:398ffe6fb765…lib/api/records/politician-records.ts(<n>,<n>): error TS2322: Type <str> is not assignable to type <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2305 ×2 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:4c6770254770…app/factcheck/[id]/layout.tsx(<n>,<n>): error TS2305: Module <str> has no exported member <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2339 ×2 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:a2b1d30276e3…lib/api/politicians/detail.ts(<n>,<n>): error TS2339: Property <str> does not exist on type <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
-
observed PROJECT_COMPILE exit 2 TS2694 ×2 1.0.1 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 sha256:a62486f02028…app/api/users/[id]/activities/route.ts(<n>,<n>): error TS2694: Namespace <str> has no exported member <str>. …typescript/tsc · compiler-diagnostic · outer npmEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-01 · Last seen: 2026-09-01
Showing the 12 most-reported of 28 recorded failure clusters. The rest are single reports.