Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen GetUnsafeString is called on input truncated at a value boundary, the parser shall propagate the error from Get without panicking.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When GetUnsafeString is called on input truncated at a value boundary, the parser shall propagate the error from Get without panicking.
the parser shall always satisfy !getunsafestring_input_is_truncated_at_value_boundary | returns_getunsafestring_error_for_truncated_value
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
GetUnsafeString delegates to Get. Truncated-at-value-boundary input must surface an error through GetUnsafeString.
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.
2 obligations · 2 discharged
Browse the catalogueBehavior for unusual but valid input combinations.
GetUnsafeString on a 1-byte truncated value returns a wrong-length raw slice that points past the value boundary, corrupting downstream byte math.
- nominalrequiredpresentCovered by 1 test
GetUnsafeString on {"a": (truncated value) propagates a stale offset from Get; the returned slice points past EOF and the caller's bytes access traverses out-of-range memory.
- 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 !getunsafestring_input_is_truncated_at_value_boundary | returns_getunsafestring_error_for_truncated_value
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| getunsafestring_input_is_truncated_at_value_boundary | — | True when GetUnsafeString is called on input truncated at a value boundary. | |
| returns_getunsafestring_error_for_truncated_value | — | True when GetUnsafeString propagates the error from Get for input truncated at a value boundary. |
Witnesses· 3 scenarios total
- TestGetUnsafeStringTruncatedValuedeep_spec_test.go:819
- TestMCDC_SYS_REQ_082_Row1_TriggerFalsemcdc_spec_witnesses_test.go:2675exercises 1 condition scenario
- TestMCDC_SYS_REQ_082_Row2_InvariantViolationmcdc_spec_witnesses_test.go:2683exercises 1 condition scenario
- TestMCDC_SYS_REQ_082_Row3_TruncatedValueErrormcdc_spec_witnesses_test.go:2691exercises 1 condition scenario
- TestObligation_SYS_REQ_082obligation_evidence_test.go:617
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.