Proof Portal

Projects

jsonparser

ProbeLabs23 findings · 123 requirements

The fastest JSON parser for Go — formally verified with ReqProof (real library, master).

All requirements
RequirementSYS-REQ-041SystemReview

When the JSON input is truncated at a value boundary (e.g., the value token ends at EOF with no closing delimiter such as '{"a":1' with no closing brace), Get shall return a parse-related error or not-found result and shall not panic or use an out-of-bounds index.

This requirement changed after its last recorded review, so approval is stale. Automated checks pass and 1/1 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 the JSON input is truncated at a value boundary (e.g., the value token ends at EOF with no closing delimiter such as '{"a":1' with no closing brace), Get shall return a parse-related error or not-found result and shall not panic or use an out-of-bounds index.

FRETish formula
the parser shall always satisfy !input_is_truncated_at_value_boundary | returns_error_for_truncated_value_boundary
View full formal model

Rationale & tags

Why this requirement exists, and how it is categorised.

PR #280 demonstrated that tokenEnd returns len(data) as a sentinel when no delimiter is found, and callers that use this sentinel as an array index without bounds checking will panic. This obligation class must be modeled explicitly.

truncationsentinelpr280

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
Leonidbugaev
Reviewed
Apr 23, 2026, 00:00 UTC

History

Created
Apr 14, 2026, 18:00 UTC · Claude · AI agent
Modified
Jul 26, 2026, 14:54 UTC · Created via CLI

Change history

Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.

Every recorded revision of this object's source — newest first, each with the commit message and its file-level diff.

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

Get on {"a":1 (no closing brace) drives tokenEnd to return len(data); an unguarded data[end+1] dereference or array-index use of the sentinel panics with index-out-of-range.

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 !input_is_truncated_at_value_boundary | returns_error_for_truncated_value_boundary

Variables

NameTypeDirectionDescription
input_is_truncated_at_value_boundaryTrue when the JSON input is truncated at a value boundary where the value token ends at EOF with no closing delimiter (e.g., '{"a":1' with no closing brace).
returns_error_for_truncated_value_boundaryTrue when Get returns a parse-related error or not-found result for input truncated at a value boundary, without panicking.

Witnesses· 3 scenarios total

  • TestMCDC_SYS_REQ_041_Row1_TriggerFalse
    exercises 1 condition scenario
  • TestMCDC_SYS_REQ_041_Row2_InvariantViolation
    exercises 1 condition scenario
  • TestMCDC_SYS_REQ_041_Row3_TruncatedError
    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
#input_is_truncated_at_value_boundaryreturns_error_for_truncated_value_boundaryResultProvesCovering test
1FFTinput_is_truncated_at_value_boundary
2TFFinput_is_truncated_at_value_boundary
3TTTreturns_error_for_truncated_value_boundary

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