Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsThe fastest JSON parser for Go — formally verified with ReqProof (real library, master).
When the current path segment is a negative array index (e.g., "[-1]"), Get shall return the defined not-found result because negative indexing is not supported by the JSON path syntax.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When the current path segment is a negative array index (e.g., "[-1]"), Get shall return the defined not-found result because negative indexing is not supported by the JSON path syntax.
the parser shall always satisfy !path_segment_is_negative_array_index | returns_not_found_for_negative_array_index
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Negative array indices are not part of the documented path syntax. The parser should deterministically handle them rather than producing undefined behavior.
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
- Leonidbugaev
- Reviewed
- Apr 23, 2026, 00:00 UTC
History
- Created
- Apr 14, 2026, 18:00 UTC · Claude · AI agent
- Modified
- Jul 26, 2026, 14:54 UTC · Created via CLI
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.
1 obligation · 1 discharged
Browse the catalogueGet on path [-1] is parsed by strconv.Atoi as -1 and then used as data[i-1] or an array element index, wrapping to a large unsigned index and panicking with index-out-of-range.
- 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 !path_segment_is_negative_array_index | returns_not_found_for_negative_array_index
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| path_segment_is_negative_array_index | — | True when the current path segment is a negative array index such as "[-1]". | |
| returns_not_found_for_negative_array_index | — | True when Get returns the defined not-found result for a negative array index because negative indexing is not supported. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_047_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_047_Row2_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_047_Row3_NegativeNotFoundexercises 1 condition scenario
MC/DC truth table· 3 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| # | path_segment_is_negative_array_index | returns_not_found_for_negative_array_index | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | path_segment_is_negative_array_index | |
| 2 | T | F | F | path_segment_is_negative_array_index | |
| 3 | T | T | T | returns_not_found_for_negative_array_index |
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 (3)
- deep_spec_test.godeep_spec_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- obligation_evidence_test.goobligation_evidence_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.