Proof Portal

Projects

jsonparser

ProbeLabs23 findings · 123 requirements
Showing the current git stateNo audit has been synced for this project yet — verification results (proof status, coverage, solver signals) appear once an audit is published.proof-demod79405e
All requirements
RequirementSYS-REQ-081SystemApproved

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

This requirement changed after its last recorded review, so approval is stale. Automated checks pass and 3/3 obligations are satisfied.
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
View full formal model

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
Strategyfretish

Review

Status
approved
Reviewer
Buger · lead_engineer
Reviewed
Aug 20, 2026, 13:11 UTC
Spec-conformance reviewed (agent:claude:spec-conformance); approved on owner authorization.

History

Created
Apr 14, 2026, 18:00 UTC · Claude · 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.

  1. Claude:spec Conformance · AI agentApprovedSpec conformanceAug 20, 2026 · last monthREVIEW-61

    Empty-input behavior mirrors Get by construction: GetUnsafeString (parser.go:2032) forwards Get's error unchanged, and Get on with a key returns KeyPathNotFoundError from searchKeysConfig's -1 result (internalGetConfig, parser.go:1672). TestGetUnsafeStringEmptyInput and MCDC rows 2/3 confirm err!=nil on empty input, while row1 shows no error on {"a":"b"}. No panic path exists because the empty slice never gets indexed before the searchKeys guard fires.

    Cited code (3)

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.

If it were 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.

If it were 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

  • TestMCDC_SYS_REQ_081_Row1_TriggerFalse
    exercises 1 condition scenario
  • TestMCDC_SYS_REQ_081_Row2_InvariantViolation
    exercises 1 condition scenario
  • TestMCDC_SYS_REQ_081_Row3_EmptyInputError
    exercises 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.

Covereda test exercises this rowExempteda reviewed mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test
#getunsafestring_input_is_emptyreturns_getunsafestring_error_for_emptyResultProvesCovering test
1FFTgetunsafestring_input_is_empty
2TFFgetunsafestring_input_is_empty
3TTTreturns_getunsafestring_error_for_empty

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

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