Proof Portal

Projects

jsonparser

ProbeLabs36 findings · 123 requirements
SYS-REQ-076SystemReview

When GetInt addresses a JSON number token whose magnitude exceeds the int64 range, the parser shall return the documented overflow error.

PriorityshallTypeguaranteeCategoryfunctionalComponentparserAssuranceEFindingsHighworst open

Specification

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

Description

When GetInt addresses a JSON number token whose magnitude exceeds the int64 range, the parser shall return the documented overflow error.

FRETish formula
the parser shall always satisfy !getint_value_overflows_int64 | returns_getint_overflow_error

Rationale & tags

Why this requirement exists, and how it is categorised.

GetInt delegates to ParseInt for conversion. Overflow at int64 boundary must be propagated through GetInt.

getintboundaryoverflow

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 at limits, thresholds, and edge-of-range values.

Worst case if violatedHigh

GetInt on 99999999999999999999 silently wraps via strconv to a negative int64 (ignoring ErrRange), producing a wrong-sign value at the caller.

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

Behavior for unusual but valid input combinations.

Worst case if violatedMedium

GetInt on a boundary value like -9223372036854775808 (INT64_MIN) negates it during parse and returns 0 or a wrong positive value; or on a canonical-form +0/-0 token returns wrong sign, corrupting accumulator 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 !getint_value_overflows_int64 | returns_getint_overflow_error

Variables

NameTypeDirectionDescription
getint_value_overflows_int64True when GetInt addresses a JSON number token whose magnitude exceeds the int64 range.
returns_getint_overflow_errorTrue when GetInt returns the documented overflow error for a value exceeding int64 range.

Witnesses· 3 scenarios total

  • TestGetIntOverflow
    deep_spec_test.go:735
  • TestMCDC_SYS_REQ_076_Row1_TriggerFalse
    mcdc_spec_witnesses_test.go:2499exercises 1 condition scenario
  • TestMCDC_SYS_REQ_076_Row2_InvariantViolation
    mcdc_spec_witnesses_test.go:2511exercises 1 condition scenario
  • TestMCDC_SYS_REQ_076_Row3_OverflowError
    mcdc_spec_witnesses_test.go:2519exercises 1 condition scenario
  • TestObligation_SYS_REQ_076
    obligation_evidence_test.go:559

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