Proof Portal

Projects

jsonparser

ProbeLabs36 findings · 123 requirements
SYS-REQ-081SystemReview

When GetUnsafeString is called on empty input, the parser shall return the same not-found or error behavior as Get on empty input.

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 is called on empty input, the parser shall return the same not-found or error behavior as Get on empty input.

FRETish formula
the parser shall always satisfy !getunsafestring_input_is_empty | returns_getunsafestring_error_for_empty

Rationale & tags

Why this requirement exists, and how it is categorised.

Empty input to GetUnsafeString delegates to Get. The empty-input behavior must be explicitly covered.

getunsafestringempty

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 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 catalogue
Discharged

Behavior when inputs are absent, nil, zero-length, or blank.

Worst case if violatedLow

GetUnsafeString on an empty []byte returns a non-empty string from a stale buffer instead of the not-found result, leaking stale memory to the caller.

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

Behavior specified when inputs are nil, null, or zero-value.

Worst case if violatedHigh

GetUnsafeString on nil data panics in nextToken at data[0] instead of returning the not-found result, crashing the caller on a nil trust-boundary input.

Discharging evidence2/2 required witnessed
  • negativerequiredpresent
    Covered by 1 test
  • 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 !getunsafestring_input_is_empty | returns_getunsafestring_error_for_empty

Variables

NameTypeDirectionDescription
getunsafestring_input_is_emptyTrue when GetUnsafeString is called on empty input.
returns_getunsafestring_error_for_emptyTrue when GetUnsafeString returns not-found or error for empty input.

Witnesses· 3 scenarios total

  • TestGetUnsafeStringEmptyInput
    deep_spec_test.go:810
  • TestMCDC_SYS_REQ_081_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:2647exercises 1 condition scenario
  • TestMCDC_SYS_REQ_081_Row2_InvariantViolation
    mcdc_spec_witnesses_test.go:2655exercises 1 condition scenario
  • TestMCDC_SYS_REQ_081_Row3_EmptyInputError
    mcdc_spec_witnesses_test.go:2663exercises 1 condition scenario
  • TestObligation_SYS_REQ_081
    obligation_evidence_test.go:605

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.

If you change this

Requirements
0
Files
1
Tests
3
At-risk contracts
0

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

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