Proof Portal

Sign in
Projects

jsonparser

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

When GetUnsafeString addresses a JSON string value, the parser shall return the addressed raw value bytes mapped directly as a Go string without JSON unescaping.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsnone open

Specification

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

Description

When GetUnsafeString addresses a JSON string value, the parser shall return the addressed raw value bytes mapped directly as a Go string without JSON unescaping.

FRETish formula
the parser shall always satisfy !addressed_value_is_string | returns_unsafe_string_view

Rationale & tags

Why this requirement exists, and how it is categorised.

GetUnsafeString is explicitly documented as the low-allocation alternative to GetString and needs its own contract coverage.

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:21 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.

1 obligation · 1 discharged

Browse the catalogue
Discharged

Output identical regardless of collection ordering or runtime conditions.

Worst case if violatedMedium

GetUnsafeString returns different raw bytes for identical input across calls, corrupting downstream byte-equality or hash invariants.

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 | returns_unsafe_string_view

Variables

NameTypeDirectionDescription
addressed_value_is_string—True when the addressed successful lookup value is a JSON string token.
returns_unsafe_string_view—True when GetUnsafeString returns the addressed raw value bytes mapped directly as a Go string without JSON unescaping.

Witnesses· 3 scenarios total

  • FuzzGetUnsafeStringNative
    fuzz_native_test.go:216
  • TestMCDC_SYS_REQ_011_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:249exercises 1 condition scenario
  • TestAdditionalFuzzHarnessCoverage
    mcdc_supplement_test.go:425
  • TestObligation_SYS_REQ_011
    obligation_evidence_test.go:180
  • TestGetUnsafeString
    parser_test.go:1539exercises 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.

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
5
At-risk contracts
0

Files to re-check (2)

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

Tests to re-run (5)

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

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