Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen the JSON input is truncated at a value boundary (e.g., the value token ends at EOF with no closing delimiter such as '{"a":1' with no closing brace), Get shall return a parse-related error or not-found result and shall not panic or use an out-of-bounds index.
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 truncated at a value boundary (e.g., the value token ends at EOF with no closing delimiter such as '{"a":1' with no closing brace), Get shall return a parse-related error or not-found result and shall not panic or use an out-of-bounds index.
the parser shall always satisfy !input_is_truncated_at_value_boundary | returns_error_for_truncated_value_boundary
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
PR #280 demonstrated that tokenEnd returns len(data) as a sentinel when no delimiter is found, and callers that use this sentinel as an array index without bounds checking will panic. This obligation class must 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
- Aug 20, 2026, 13:11 UTC
History
- Created
- Apr 14, 2026, 18:00 UTC · Claude · AI agent
- Modified
- Aug 20, 2026, 13:11 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.
Review history
Human and AI-agent approvals of this requirement — the 'why was this approved' lineage, each with the reviewer's justification and the code it cites.
- Claude:spec Conformance · AI agentApprovedSpec conformanceAug 20, 2026 · last monthREVIEW-23
The invariant
!input_is_truncated_at_value_boundary | returns_error_for_truncated_value_boundaryrequires Get to return an error/not-found without panicking on input truncated at a value boundary. Get (parser.go:1659) delegates to internalGetConfig, which returns MalformedJsonError when nextTokenConfig hits end-of-buffer (parser.go:1680-1682) and returns getType's error otherwise, all via bounded index scans, so{"test":yields MalformedJsonError and{"test":1best-effort matches the number with no panic. searchKeysConfig and stringEndConfig both return -1 rather than indexing pastlen(data)on truncation. TestTruncatedAtValueBoundary and the MCDC rows confirm no panic, and no KI is attached.Cited code (4)
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 {"a":1 (no closing brace) drives tokenEnd to return len(data); an unguarded data[end+1] dereference or array-index use of the sentinel panics 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 !input_is_truncated_at_value_boundary | returns_error_for_truncated_value_boundary
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| input_is_truncated_at_value_boundary | — | True when the JSON input is truncated at a value boundary where the value token ends at EOF with no closing delimiter (e.g., '{"a":1' with no closing brace). | |
| returns_error_for_truncated_value_boundary | — | True when Get returns a parse-related error or not-found result for input truncated at a value boundary, without panicking. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_041_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_041_Row2_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_041_Row3_TruncatedErrorexercises 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| # | input_is_truncated_at_value_boundary | returns_error_for_truncated_value_boundary | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | input_is_truncated_at_value_boundary | |
| 2 | T | F | F | input_is_truncated_at_value_boundary | |
| 3 | T | T | T | returns_error_for_truncated_value_boundary |
Its place
How this requirement connects — what proves it, what it affects, and what it rests on. Authored links only here; automatically derived links come from the audit index.
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 — authored trace links only (automatically derived links come from the audit index and aren't shown here).
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
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.