Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen the JSON input is well formed, a key path is provided, and the addressed path does not exist, the parser shall return the defined not-found result with `NotExist`, offset `-1`, and `KeyPathNotFoundError`.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When the JSON input is well formed, a key path is provided, and the addressed path does not exist, the parser shall return the defined not-found result with `NotExist`, offset `-1`, and `KeyPathNotFoundError`.
the parser shall always satisfy !json_input_is_well_formed | !key_path_is_provided | addressed_path_exists | returns_missing_path_result_for_well_formed_lookup
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
The Get contract is not complete unless the missing-path outcome is specified independently from successful lookup and incomplete-input failure.
Verification & provenance
How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).
Review
- Status
- approved
- Reviewer
- human:buger · lead_engineer
- Reviewed
- Jul 26, 2026, 18:45 UTC
History
- Created
- Apr 14, 2026, 00:00 UTC · human:cli
- Modified
- Jul 26, 2026, 18:58 UTC · human:cli
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
3 obligations · 3 discharged
Browse the catalogueGet returns a stale value slice from a previously cached offset instead of KeyPathNotFoundError when the path is missing, leaking a sibling field's bytes to the caller (silent data corruption).
- nominalrequiredpresentCovered by 1 test
Behavior specified when inputs are nil, null, or zero-value.
An empty-string key component flowing into searchKeys on nil-or-zero-length internal slices triggers an unguarded keys[i][0] / p[level][0] dereference, crashing the goroutine (OSS-Fuzz 4649128545288192 panic class, SYS-REQ-111 hazard).
- negativerequiredpresentCovered by 1 test
- nominalrequiredpresentCovered by 1 test
An empty-string key component is structurally a no-effective-path case; if the early guard regresses the keys[i][0] dereference panics with index-out-of-range on the empty component slice (SYS-REQ-111 hazard class).
- nominalrequiredpresentCovered by 1 test
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
FRETish formula
the parser shall always satisfy !json_input_is_well_formed | !key_path_is_provided | addressed_path_exists | returns_missing_path_result_for_well_formed_lookup
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| json_input_is_well_formed | — | True when the provided JSON byte slice is well formed for the lookup case under evaluation. | |
| key_path_is_provided | — | True when the caller supplies at least one key-path segment for the lookup case under evaluation. | |
| addressed_path_exists | — | True when the requested key path resolves to a value in the JSON input under evaluation. | |
| returns_missing_path_result_for_well_formed_lookup | — | True when Get reports the defined not-found outcome for a well-formed lookup whose addressed path does not exist. |
Witnesses· 5 scenarios total
- TestGetNotFoundResultdeep_spec_test.go:954
- TestGetEmptyKeyPathComponentempty_key_path_test.go:37
- TestTypedGetEmptyKeyPathComponentempty_key_path_test.go:79
- TestMCDC_SYS_REQ_016_Row1_TriggerFalsemcdc_spec_witnesses_test.go:333exercises 1 condition scenario
- TestMCDC_SYS_REQ_016_Row2_NoKeyPathmcdc_spec_witnesses_test.go:345exercises 1 condition scenario
- TestMCDC_SYS_REQ_016_Row3_InvariantViolationmcdc_spec_witnesses_test.go:360exercises 1 condition scenario
- TestMCDC_SYS_REQ_016_Row4_MissingPathResultmcdc_spec_witnesses_test.go:375exercises 1 condition scenario
- TestMCDC_SYS_REQ_016_Row5_AddressedPathExistsmcdc_spec_witnesses_test.go:387exercises 1 condition scenario
- TestObligation_SYS_REQ_016obligation_evidence_test.go:217
- TestGetRequirementSlicesparser_test.go:1390
- TestMCDC_SYS_REQ_111_Row5_EmptyKeyReturnsNotFoundNoPanicsys_req_110_111_witness_test.go:212
- TestObligation_SYS_REQ_111_NilSafety_Negativesys_req_110_111_witness_test.go:320
- TestObligation_SYS_REQ_111_NoPathProvided_Nominalsys_req_110_111_witness_test.go:363
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.
Impact
Blast radius — if you change this requirement, what else may need re-checking, and what it in turn depends on.
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
Files to re-check (1)
- parser.goparser.go
Tests to re-run (6)
- deep_spec_test.godeep_spec_test.go
- empty_key_path_test.goempty_key_path_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- obligation_evidence_test.goobligation_evidence_test.go
- parser_test.goparser_test.go
- sys_req_110_111_witness_test.gosys_req_110_111_witness_test.go
What this rests on
Parent requirements (1)
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.