Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen ParseInt receives an integer token whose magnitude exceeds the supported int64 range, the parser shall return the documented overflow error.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ParseInt receives an integer token whose magnitude exceeds the supported int64 range, the parser shall return the documented overflow error.
the parser shall always satisfy !raw_int_token_overflows_int64 | returns_parseint_overflow_error
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Overflow is an externally visible ParseInt outcome and should be specified independently from valid integer parsing and malformed-token rejection.
Verification & provenance
How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).
Review
- Status
- approved
- Reviewer
- Buger · lead_engineer
- Reviewed
- Aug 20, 2026, 13:11 UTC
History
- Created
- Apr 14, 2026, 15:45 UTC · Codex · 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.
- Claude:spec Conformance · AI agentApprovedSpec conformanceAug 20, 2026 · last monthREVIEW-94
The invariant
!raw_int_token_overflows_int64 | returns_parseint_overflow_errorrequires an int64-overflowing token to yield OverflowIntegerError, and ParseInt (parser.go:2168) correctly surfaces OverflowIntegerError when parseInt reports overflow. The defect is in parseInt: its fast-path digit-count gate isif l-i < 20instead of< 19(bytes.go:27), so a 19-digit value takes the unchecked int64 accumulation loop that wraps silently and returns (wrapped, true, false) with no overflow signal, so ParseInt returns a wrong value and nil error for e.g. 9999999999999999999. This is the intentional overflow defect tracked by KI-7 (CWE-190), witnessed by TestDemoKI7 and the MCDC Row2 invariant-violation test. Wrapper is correct; tracked overflow-check defect makes verification honestly fail — approvable.Cited code (2)
Open known issues
Findings currently open against this requirement — issues its verification surfaced that are not resolved yet. Each links to the full finding.
+1 resolved — see the Findings tab under Trace evidence.
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 catalogueBehavior at limits, thresholds, and edge-of-range values.
ParseInt on 99999999999999999999 silently wraps via strconv to a negative int64 (ignoring ErrRange), producing a wrong-sign value at the caller.
- nominalrequiredpresentCovered 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).
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 !raw_int_token_overflows_int64 | returns_parseint_overflow_error
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| raw_int_token_overflows_int64 | — | True when ParseInt receives an integer token whose magnitude exceeds the supported int64 range. | |
| returns_parseint_overflow_error | — | True when ParseInt returns the documented overflow error for an integer token outside the supported int64 range. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_039_Row1_NoOverflowexercises 1 condition scenario
- TestMCDC_SYS_REQ_039_Row2_InvariantViolationexercises 1 condition scenario
- TestParseIntexercises 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.
mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test| # | raw_int_token_overflows_int64 | returns_parseint_overflow_error | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | raw_int_token_overflows_int64 | |
| 2 | T | F | F | raw_int_token_overflows_int64 | |
| 3 | T | T | T | returns_parseint_overflow_error |
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).
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
If you change this
Files to re-check (1)
- parser.goparser.go
Tests to re-run (3)
- 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
Parent requirements (1)
Changes
Semantic changes that move or scope this requirement — the intended work touching it. Each links to the full change.
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.