Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen ParseString receives a malformed encoded string literal, the parser shall return the documented malformed-value error.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ParseString receives a malformed encoded string literal, the parser shall return the documented malformed-value error.
the parser shall always satisfy raw_string_literal_is_well_formed | returns_parsestring_error
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Malformed-string failure is externally visible and should be specified independently from valid ParseString decoding 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
- Buger · lead_engineer
- Reviewed
- Aug 20, 2026, 13:11 UTC
History
- Created
- Apr 14, 2026, 15:45 UTC · Codex · 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-93
The invariant
raw_string_literal_is_well_formed | returns_parsestring_errorrequires ParseString to return MalformedValueError on a malformed encoded literal, and the wrapper at parser.go:2147 does exactly that whenever Unescape reports an error. But the Unescape internals carry two intentional out-of-bounds defects on malformed input: decodeSingleUnicodeEscape guardsif len(in) < 4instead of 6 (escape.go:88) so a truncated\u00indexes in[4]/in[5] and panics (KI-5), and unescapeToUTF8Config guardsif len(in) < 1instead of 2 (escape.go:194) so a lone trailing backslash reads in[1] and panics (KI-6). For those malformed literals the code panics rather than returning the documented error, violating the invariant; both are tracked, open, high-severity KIs, so the requirement is sound-but-honestly-failing and approvable. (KI-14, dropping/from the escape switch at escape.go:203, is a false-reject of valid input and does not affect this malformed->error direction.)Cited code (3)
Open known issues
Findings currently open against this requirement — issues its verification surfaced that are not resolved yet. Each links to the full finding.
- HighOpen
decodeSingleUnicodeEscape length guard too small — OOB read + panic on a truncated \uXX escape
KI-5
- HighOpen
unescapeToUTF8Config length guard off-by-one — OOB panic reading in[1] on a lone trailing backslash
KI-6
- LowOpen
unescapeToUTF8Config drops '/' from the accepted escapes — the valid JSON escape `\/` is rejected as malformed
KI-14
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
The tests that discharge each obligation need a synced audit
The evidence matrix behind each obligation comes from the audit index, which is produced by running an audit — not read from git. Nothing here means unknown — not that the requirement has no obligations.
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_error
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_error | — | True when ParseString returns the documented malformed-value error for a malformed encoded string literal. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_038_Row1_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_038_Row2_WellFormedexercises 1 condition scenario
- TestParseStringexercises 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| # | raw_string_literal_is_well_formed | returns_parsestring_error | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | F | raw_string_literal_is_well_formed | |
| 2 | F | T | T | returns_parsestring_error | |
| 3 | T | F | T | raw_string_literal_is_well_formed |
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 (2)
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_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.