Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsThe fastest JSON parser for Go — formally verified with ReqProof (real library, master).
When the input is empty and a key path is provided, 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 input is empty and a key path is provided, the parser shall return the defined not-found result with `NotExist`, offset `-1`, and `KeyPathNotFoundError`.
the parser shall always satisfy !json_input_is_empty | !key_path_is_provided | returns_missing_path_result_for_empty_input
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
The current Get contract treats empty input as an addressed lookup miss rather than as a parsing error, so that edge case should be modeled explicitly.
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
- Buger · lead_engineer
- Reviewed
- Jul 26, 2026, 15:21 UTC
History
- Created
- Apr 14, 2026, 00:00 UTC · Created via CLI
- Modified
- Jul 26, 2026, 15:21 UTC · Buger
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
Every recorded revision of this object's source — newest first, each with the commit message and its file-level diff.
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
2 obligations · 2 discharged
Browse the catalogueBehavior when inputs are absent, nil, zero-length, or blank.
Get on a zero-length input with a path returns a stale value slice instead of KeyPathNotFoundError, mis-classifying empty input as a found path and leaking stale bytes.
- nominalrequiredpresentCovered by 1 test
Behavior specified when inputs are nil, null, or zero-value.
Get on nil data panics in nextToken at data[0] instead of returning NotExist with KeyPathNotFoundError, crashing the caller on a nil trust-boundary input.
- negativerequiredpresentCovered by 1 test
- 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_empty | !key_path_is_provided | returns_missing_path_result_for_empty_input
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| json_input_is_empty | — | True when the provided lookup input is empty. | |
| key_path_is_provided | — | True when the caller supplies at least one key-path segment for the lookup case under evaluation. | |
| returns_missing_path_result_for_empty_input | — | True when Get reports the defined not-found outcome for an empty input with a provided key path. |
Witnesses· 4 scenarios total
- TestMCDC_SYS_REQ_019_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_019_Row2_EmptyNoKeyPathexercises 1 condition scenario
- TestMCDC_SYS_REQ_019_Row3_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_019_Row4_EmptyMissingPathexercises 1 condition scenario
MC/DC truth table· 4 rows
Each row assigns the formula's conditions (T/F) and shows the Result— the formula's value for that input row, not a test pass/fail. A row proves a condition when flipping only that condition flips the outcome. The test that covers each row is linked.
mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test| # | json_input_is_empty | key_path_is_provided | returns_missing_path_result_for_empty_input | Result | Proves | Covering test |
|---|---|---|---|---|---|---|
| 1 | F | T | F | T | json_input_is_empty | |
| 2 | T | F | F | T | key_path_is_provided | |
| 3 | T | T | F | F | json_input_is_empty | |
| 4 | T | T | T | T | returns_missing_path_result_for_empty_input |
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 (4)
- deep_spec_test.godeep_spec_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- obligation_evidence_test.goobligation_evidence_test.go
- parser_test.goparser_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.