Recordsnpmzod4.4.3Client.prototype.callTool
Change the conditions
Current conditions
Client.prototype.callTool @4.4.3alpine musl · x64 · node 22 · npm · node
3 of 3 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (2)
- Project observations
- nothing at this coordinate
- Contract verifications
- 3 / 3
- Cross-checked
- reproduced by two or more independent peers
- Last recorded
- 2026-09-07
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 PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×16 3.25.76 → 4.1.12 → 4.4.3 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-13 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 4.4.3 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 4.4.3 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:9be950af9140…Traceback (most recent call last): · File <str>, line 1, in <module> · ModuleNotFoundError: No module named <str>python3 · unclassified-diagnostic · outer python3 · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate