Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen ParseString receives a well-formed raw JSON string literal body, the parser shall return the corresponding decoded Go string value.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ParseString receives a well-formed raw JSON string literal body, the parser shall return the corresponding decoded Go string value. Escape is the RFC 8259 inverse of Unescape/ParseString: Escape(in) returns in encoded as a JSON string literal including the surrounding quotation marks, escaping the mandatory characters (quotation mark, reverse solidus, control characters U+0000–U+001F) and any non-ASCII bytes as \uXXXX sequences, so the result is a valid JSON string token suitable for direct embedding in a JSON document.
the parser shall always satisfy !raw_string_literal_is_well_formed | returns_parsestring_value
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
ParseString success on valid encoded strings should be specified independently from malformed-string rejection.
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:buger · lead_engineer
- Reviewed
- Jul 27, 2026, 11:43 UTC
History
- Created
- Apr 13, 2026, 17:21 UTC · human:cli
- Modified
- Jul 27, 2026, 11:43 UTC · human:buger
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 catalogueBehavior specified for encoding and decoding round-trips.
ParseString on a raw body containing a malformed UTF-8 sequence (e.g. a lone surrogate) returns a Go string with invalid runes; the caller re-serializes it as invalid JSON or panics in encoding-aware downstream like bufio.
- 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 !raw_string_literal_is_well_formed | returns_parsestring_value
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| raw_string_literal_is_well_formed | — | True when ParseString receives a well-formed raw JSON string literal body. | |
| returns_parsestring_value | — | True when ParseString returns the corresponding decoded Go string value. |
Witnesses· 3 scenarios total
- TestRemoval3_DecodeSingleUnicodeEscape_MaxValuedead_code_audit_test.go:202
- TestRemoval3_DecodeSingleUnicodeEscape_MinValuedead_code_audit_test.go:218
- TestRemoval3_DecodeUnicodeEscape_BMP_NonSurrogatedead_code_audit_test.go:229
- TestRemoval3_DecodeUnicodeEscape_HighSurrogateAlonedead_code_audit_test.go:241
- TestRemoval3_DecodeUnicodeEscape_ValidSurrogatePairdead_code_audit_test.go:255
- TestRemoval3_MathematicalProofdead_code_audit_test.go:267
- TestRemoval1_Unescape_LoopExitsOnSingleEscapedead_code_audit_test.go:38
- TestRemoval1_Unescape_LoopExitsOnTrailingEscapedead_code_audit_test.go:49
- TestRemoval1_Unescape_InvalidEscapedead_code_audit_test.go:769
- TestRemoval1_Unescape_ConsecutiveEscapesdead_code_audit_test.go:777
- TestRemoval1_Unescape_EscapedQuotedead_code_audit_test.go:788
- TestH2Iescape_test.go:10
- TestUnescapeescape_test.go:170
- TestUnescapeLoneHighSurrogateescape_test.go:232
- TestUnescapeLoneHighSurrogateFollowedByNonEscapeescape_test.go:244
- TestUnescapeLoneLowSurrogateescape_test.go:256
- TestUnescapeHighSurrogateThenNonSurrogateescape_test.go:267
- TestUnescapeValidSurrogatePairStillWorksescape_test.go:279
- TestParseStringLoneSurrogateMatchesEncodingJSONescape_test.go:291
- TestDecodeSingleUnicodeEscapeescape_test.go:74
- TestDecodeUnicodeEscapeescape_test.go:91
- FuzzParseStringNativefuzz_native_test.go:120
- TestMCDC_SYS_REQ_014_Row1_TriggerFalsemcdc_spec_witnesses_test.go:299exercises 1 condition scenario
- TestParseStringAndEscapeSupplementalCoveragemcdc_supplement_test.go:366
- TestFuzzParseStringHarnessCoveragemcdc_supplement_test.go:385
- TestCodeMCDC_UnescapeLoopEntrymcdc_supplement_test.go:695
- TestObligation_SYS_REQ_014obligation_evidence_test.go:198
- TestParseStringparser_test.go:2341exercises 2 condition scenarios
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 (3)
- escape.goescape.go
- fuzz.gofuzz.go
- parser.goparser.go
Tests to re-run (7)
- dead_code_audit_test.godead_code_audit_test.go
- escape_test.goescape_test.go
- fuzz_native_test.gofuzz_native_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- mcdc_supplement_test.gomcdc_supplement_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.