Records/npm/parse-conflict-json/4.0.0/parseConflictJson

Published samples

• parse-conflict-json 4.0.0: parseConflictJson Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWparseConflictJson MIT-0 · 2026-10-18

Compatibility matrix

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.

snapshot · 2026-10-19

Failure clusters

• observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 4.0.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:43caf7a060e7…
  node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
  node · unclassified-diagnostic · outer node · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18
  Diagnostic re-verification candidate
  Where does this failure start and stop?
• observed UNKNOWN exit 1 Evidence gap ×1 4.0.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:a2035c1b96ba…
  <url> · import parseConflictJson, { isDiff } from <str>; · ^^^^^^ …
  node · unclassified-diagnostic · outer node · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-10-18
  Diagnostic re-verification candidate
  Where does this failure start and stop?