Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen the JSON input is truncated in the middle of a key string (e.g., '{"a' where the key string is not terminated), Get shall return a parse-related error and shall not panic.
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 in the middle of a key string (e.g., '{"a' where the key string is not terminated), Get shall return a parse-related error and shall not panic.
the parser shall always satisfy !input_is_truncated_mid_key | returns_error_for_truncated_mid_key
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Truncated mid-key input exercises stringEnd returning -1, which is a distinct truncation pattern from mid-structure and at-value-boundary cases.
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:leonidbugaev
- Reviewed
- Apr 23, 2026, 00:00 UTC
History
- Created
- Apr 14, 2026, 18:00 UTC · agent:claude
- Modified
- Jul 26, 2026, 14:54 UTC · human:cli
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 (unclosed key string) drives stringEnd to return -1; the unguarded break leaves i past EOF and a subsequent data[i] dereference 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_mid_key | returns_error_for_truncated_mid_key
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| input_is_truncated_mid_key | — | True when the JSON input is truncated in the middle of a key string where the key is not terminated by a closing quote. | |
| returns_error_for_truncated_mid_key | — | True when Get returns a parse-related error for input truncated mid-key, without panicking. |
Witnesses· 3 scenarios total
- TestTruncatedMidKeydeep_spec_test.go:75
- TestMCDC_SYS_REQ_043_Row1_TriggerFalsemcdc_spec_witnesses_test.go:1487exercises 1 condition scenario
- TestMCDC_SYS_REQ_043_Row2_InvariantViolationmcdc_spec_witnesses_test.go:1495exercises 1 condition scenario
- TestMCDC_SYS_REQ_043_Row3_TruncatedErrormcdc_spec_witnesses_test.go:1503exercises 1 condition scenario
- TestObligation_SYS_REQ_043obligation_evidence_test.go:385
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.