Proof Portal

Sign in
Projects

jsonparser

ProbeLabs36 findings · 123 requirements
All requirements
SYS-REQ-002SystemReview

When GetString addresses a JSON string value whose raw token is well formed, the parser shall return the corresponding decoded Go string value.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsnone open

Specification

The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.

Description

When GetString addresses a JSON string value whose raw token is well formed, the parser shall return the corresponding decoded Go string value.

FRETish formula
the parser shall always satisfy !addressed_value_is_string | !raw_string_token_is_well_formed | returns_getstring_decoded_value

Rationale & tags

Why this requirement exists, and how it is categorised.

GetString is the documented safe string helper and is expected to handle escaped and Unicode content correctly.

Verification & provenance

How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).

Assurance levelE
Formalizationvalid
Realizabilityrealizable
Vacuitychecked_ok
Strategyfretish

Review

Status
approved
Reviewer
human:leonidbugaev
Reviewed
Apr 23, 2026, 00:00 UTC

History

Created
Apr 13, 2026, 17:10 UTC · human:cli
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.

3 obligations · 3 discharged

Browse the catalogue
Discharged

Output identical regardless of collection ordering or runtime conditions.

Worst case if violatedMedium

GetString returns a different decoded string across calls on identical well-formed input, corrupting cache keys or byte-equality assumptions at the call site.

Discharging evidence1/1 required witnessed
  • nominalrequiredpresent
    Covered by 1 test
Discharged

Behavior for unusual but valid input combinations.

Worst case if violatedLow

GetString on a 1-char escaped body like an empty quoted string returns an out-of-range slice or wrong length, corrupting downstream string math at the caller.

Discharging evidence1/1 required witnessed
  • nominalrequiredpresent
    Covered by 1 test
Discharged

Behavior specified for encoding and decoding round-trips.

Worst case if violatedHigh

GetString on a body containing invalid UTF-8 (e.g. a lone surrogate like \uDDDD) returns a Go string with invalid runes; the caller re-serializes it as invalid JSON or panics in encoding-aware downstream.

Discharging evidence1/1 required witnessed
  • nominalrequiredpresent
    Covered 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).

FRETish formula

the parser shall always satisfy !addressed_value_is_string | !raw_string_token_is_well_formed | returns_getstring_decoded_value

Variables

NameTypeDirectionDescription
addressed_value_is_string—True when the addressed successful lookup value is a JSON string token.
raw_string_token_is_well_formed—True when the addressed raw JSON string token is well formed and can be decoded.
returns_getstring_decoded_value—True when GetString returns the addressed value as a decoded Go string.

Witnesses· 4 scenarios total

  • FuzzGetStringNative
    fuzz_native_test.go:184
  • TestMCDC_SYS_REQ_002_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:66exercises 1 condition scenario
  • TestAdditionalFuzzHarnessCoverage
    mcdc_supplement_test.go:425
  • TestObligation_SYS_REQ_002
    obligation_evidence_test.go:113
  • TestGetString
    parser_test.go:1520exercises 3 condition scenarios
  • TestPropertyTypedAccessorsRoundTrip
    property_test.go:205

Its place

This requirement shown inside its trace neighbourhood — the parents it satisfies, the code and tests attached to it, and its findings.

Open in graph

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.

If you change this

Requirements
0
Files
2
Tests
7
At-risk contracts
0

Files to re-check (2)

  • fuzz.gofuzz.go
  • parser.goparser.go

Tests to re-run (7)

  • 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
  • property_test.goproperty_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.

Sign in to discuss this with the proof team.Sign in