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-027SystemApproved

When the addressed token cannot be classified as string, object, array, number, boolean, or null, Get shall return a value-type error instead of a successful classification.

This requirement changed after its last recorded review, so approval is stale. Automated checks pass and 1/1 obligations are satisfied.
PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceBFindingsnone open

Specification

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

Description

When the addressed token cannot be classified as string, object, array, number, boolean, or null, Get shall return a value-type error instead of a successful classification.

FRETish formula
the parser shall always satisfy !addressed_token_shape_is_invalid | returns_value_type_error
View full formal model

Rationale & tags

Why this requirement exists, and how it is categorised.

Unknown token classification is an externally visible error path in Get and should not be hidden inside a generic parse-failure bucket.

decompositiongettype

Verification & provenance

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

Assurance levelB
Formalizationvalid
Realizabilityrealizable
Vacuitychecked_ok
Strategyfretish

Review

Status
approved
Reviewer
Buger · lead_engineer
Reviewed
Jul 26, 2026, 15:21 UTC
Final re-approval after L3 strict posture sweep (hazard+obligation+coverage work)

History

Created
Apr 14, 2026, 00:00 UTC · Created via CLI
Modified
Jul 26, 2026, 15:21 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.

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 violatedMedium

Get on a leading-byte token that matches no classifier (e.g. ; at value position) returns a Number or String classification anyway, mis-routing the caller into the wrong typed accessor and producing wrong downstream values.

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_token_shape_is_invalid | returns_value_type_error

Variables

NameTypeDirectionDescription
addressed_token_shape_is_invalidTrue when the addressed token cannot be classified as string, object, array, number, boolean, or null.
returns_value_type_errorTrue when Get returns a value-type classification error for an invalid addressed token shape.

Witnesses· 3 scenarios total

  • TestMCDC_SYS_REQ_027_Row1_TriggerFalse
    exercises 1 condition scenario
  • TestMCDC_SYS_REQ_027_Row2_InvariantViolation
    exercises 1 condition scenario
  • TestMCDC_SYS_REQ_027_Row3_ValueTypeError
    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
#addressed_token_shape_is_invalidreturns_value_type_errorResultProvesCovering test
1FFTaddressed_token_shape_is_invalid
2TFFaddressed_token_shape_is_invalid
3TTTreturns_value_type_error

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

Files to re-check (1)

  • parser.goparser.go

Tests to re-run (4)

  • deep_spec_test.godeep_spec_test.go
  • mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
  • obligation_evidence_test.goobligation_evidence_test.go
  • parser_test.goparser_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