Records/npm/ip-address/10.7.2

Environment detail

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

Recent failure clusters

• observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 10.7.2 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:e5d62c8db895…
  AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · 0 !== 1 · at TestContext.<anonymous> (<url>) …
  javascript/test-runner · test-runner-diagnostic · outer npm test
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-17 · Last seen: 2026-09-17
  Where does this failure start and stop?
• observed UNKNOWN exit 1 Evidence gap ×1 10.7.2 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 sha256:21906f5c9d5c…
  <str> is not recognized as an internal or external command, · operable program or batch file. · > rdcx@0.1.0 typecheck · > tsc --noEmit
  npm · unclassified-diagnostic · outer npm run · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-26 · Last seen: 2026-09-26
  Diagnostic re-verification candidate
  Where does this failure start and stop?

Symbols

No symbols with evidence yet.