Proof Portal

Projects

jsonparser

ProbeLabs36 findings · 123 requirements
STK-REQ-004StakeholderReview

Library users shall traverse arrays and objects and extract multiple key paths from one payload without manually walking the JSON structure.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsnone open

Specification

The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.

Description

Library users shall traverse arrays and objects and extract multiple key paths from one payload without manually walking the JSON structure.

Rationale & tags

Why this requirement exists, and how it is categorised.

The traversal helpers and EachKey are part of the library's value proposition for dynamic JSON inspection without struct predeclaration or hand-written walkers.

traversaldecompositionparserdeserializeraccepts_user_data

Verification & provenance

How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).

Assurance levelE
Formalizationnone
Vacuitychecked_ok
Strategyinformal

Review

Status
approved
Reviewer
human:leonidbugaev
Reviewed
Apr 23, 2026, 00:00 UTC

History

Created
Apr 13, 2026, 17:10 UTC · human:cli
Modified
Jul 26, 2026, 12:54 UTC · human:cli

Obligations

What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.

11 obligations · 11 discharged

Browse the catalogue
Discharged
Worst case if violatedHigh

If ObjectEach/ArrayEach swallow a callback returned error and continue iterating, the next iteration invokes the callback on stale offset state, corrupting traversal and dereferencing past the buffer end.

Discharging evidence0/0 required witnessed
  • nominalrecommendedpresent
    Covered by 1 test
    via SYS-REQ-052
Discharged

Output identical regardless of collection ordering or runtime conditions.

Worst case if violatedMedium

EachKey callback order on identical input must be deterministic; a regression in pathFlags match order produces callbacks in different order across calls, breaking deterministic processing.

Discharging evidence0/0 required witnessed
  • nominalrecommendedpresent
    Covered by 1 test
    via SYS-REQ-006
Discharged

Behavior for unusual but valid input combinations.

Worst case if violatedMedium

ArrayEach on a single-element array must invoke the callback exactly once; a regression in the post-callback offset arithmetic invokes it twice or zero times, breaking the count contract.

Discharging evidence0/0 required witnessed
  • nominalrecommendedpresent
    Covered by 1 test
    via SYS-REQ-008
Discharged

Behavior when inputs are absent, nil, zero-length, or blank.

Worst case if violatedHigh

ArrayEach on a zero-length []byte returns MalformedObjectError via the early guard; if the guard regresses nextToken returns -1 and the follow-on data[offset] dereference panics on the empty slice.

Discharging evidence0/0 required witnessed
Discharged

Behavior when inputs are syntactically or structurally invalid.

Worst case if violatedHigh

ArrayEach on adversarial JSON like [1,2,,] drives Get to a parse error mid-array; if the error-propagation guard regresses the loop continues past the malformed token and dereferences data[offset] past len(data).

Discharging evidence1/1 required witnessed
Discharged

Behavior specified when inputs are nil, null, or zero-value.

Worst case if violatedHigh

ObjectEach(nil,...) flows through searchKeys nil-slice loop; the subsequent nextToken/data[offset] dereference panics with nil-slice index-out-of-range.

Discharging evidence1/1 required witnessed
  • negativerequiredpresent
    Covered by 2 tests
    via SYS-REQ-028
  • nominalrecommendedpresent
    Covered by 1 test
    via SYS-REQ-028
Discharged

Happy-path behavior with valid inputs.

Discharging evidence0/0 required witnessed
Discharged
Worst case if violatedHigh

When searchKeys or blockEnd returns -1 sentinel for malformed structure, ArrayEach/EachKey dereference data[offset] without re-checking offset>=0 (the OSS-Fuzz Delete panic class).

Discharging evidence0/0 required witnessed
  • nominalrecommendedpresent
    Covered by 1 test
    via SYS-REQ-085
Discharged
Worst case if violatedHigh

Truncated JSON like [1,2 with no closing bracket drives nextToken in ArrayEach to -1; the follow-on data[offset] dereference panics with index-out-of-range on the truncated remainder.

Discharging evidence0/0 required witnessed
  • nominalrecommendedpresent
    Covered by 1 test
    via SYS-REQ-083
Discharged
Worst case if violatedHigh

Truncated JSON like [1,"abc with no closing string mid-element drives Get to stringEnd returning -1; the follow-on data[offset] dereference in ArrayEach panics past the buffer end.

Discharging evidence0/0 required witnessed
  • nominalrecommendedpresent
    Covered by 1 test
    via SYS-REQ-053
Discharged
Worst case if violatedHigh

Truncated JSON like {"a":[1,2 with no matching close bracket drives blockEnd to -1; if the guard regresses the unbounded loop dereferences past the buffer end, crashing the process.

Discharging evidence0/0 required witnessed
  • nominalrecommendedpresent
    Covered by 1 test
    via SYS-REQ-084

Acceptance criteria

Stakeholder conditions for satisfaction, traced to the derived requirements and evidence that discharge them.

Stakeholder-authored conditions defining when the requirement is satisfied, traced to derived requirements / evidence.

Its place

This requirement shown inside its trace neighbourhood — the parents it satisfies, the code and tests attached to it, and its findings.

Loading graph…

Trace evidence

The concrete artifacts linked to this requirement — implementing code, verifying tests, documents, and the findings raised against it.

No implementation linked

No source files are traced to this requirement yet.

Impact

Blast radius — if you change this requirement, what else may need re-checking, and what it in turn depends on.

If you change this

Requirements
22
Files
7
Tests
26
At-risk contracts
0

Requirements (22)

Files to re-check (7)

  • aliases.goaliases.go
  • parser.goparser.go
  • fuzz.gofuzz.go
  • wildcard.gowildcard.go
  • config.goconfig.go
  • escape.goescape.go
  • reader_parser.goreader_parser.go

Tests to re-run (26)

  • benchmark_large_payload_test.gobenchmark/benchmark_large_payload_test.go
  • benchmark_medium_payload_test.gobenchmark/benchmark_medium_payload_test.go
  • benchmark_small_payload_test.gobenchmark/benchmark_small_payload_test.go
  • obligation_evidence_test.goobligation_evidence_test.go
  • parser_test.goparser_test.go
  • aliases_test.goaliases_test.go
  • dead_code_audit_oob_test.godead_code_audit_oob_test.go
  • dead_code_audit_test.godead_code_audit_test.go
  • mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
  • mcdc_supplement_test.gomcdc_supplement_test.go
  • property_test.goproperty_test.go
  • coverage_closure_test.gocoverage_closure_test.go
  • fuzz_native_test.gofuzz_native_test.go
  • path_fuzz_test.gopath_fuzz_test.go
  • array_each_err_test.goarray_each_err_test.go
  • empty_key_path_test.goempty_key_path_test.go
  • issues_56_107_229_test.goissues_56_107_229_test.go
  • parser_error_test.goparser_error_test.go
  • v131_regression_test.gov131_regression_test.go
  • deep_spec_test.godeep_spec_test.go
  • obligation_property_test.goobligation_property_test.go
  • len_uint_test.golen_uint_test.go
  • wildcard_test.gowildcard_test.go
  • config_test.goconfig_test.go
  • v150_mcdc_witness_test.gov150_mcdc_witness_test.go
  • reader_parser_test.goreader_parser_test.go

What this rests on

Discussions

Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.

Sign in to discuss this with the proof team.Sign in