Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsWhen GetInt addresses a JSON number token whose magnitude exceeds the 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 GetInt addresses a JSON number token whose magnitude exceeds the int64 range, the parser shall return the documented overflow error.
the parser shall always satisfy !getint_value_overflows_int64 | returns_getint_overflow_error
Rationale & tags
Why this requirement exists, and how it is categorised.
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.
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, 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.
- Claude:spec Conformance · AI agentApprovedSpec conformanceAug 20, 2026 · last monthREVIEW-56
GetInt delegates magnitude checking to ParseInt, which is supposed to return OverflowIntegerError when parseInt reports overflow (parser.go:2170-2172). The overflow-checked slow path in parseInt is correct, but the fast-path gate was widened from
l-i < 19tol-i < 20(bytes.go:27), so a 19-digit literal above math.MaxInt64 (e.g. 9999999999999999999) takes the unchecked int64 fast path and wraps silently to a wrong value with a nil error instead of OverflowIntegerError. That is a genuine, reproducer-grade violation of !getint_value_overflows_int64 | returns_getint_overflow_error, but it is honestly tracked as KI-7 (high, CWE-190) whose affected_requirements includes SYS-REQ-076, so it is approvable as a tracked defect rather than an untracked failure.Cited code (4)
Open known issues
Findings currently open against this requirement — issues its verification surfaced that are not resolved yet. Each links to the full finding.
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 catalogueBehavior at limits, thresholds, and edge-of-range values.
GetInt on 99999999999999999999 silently wraps via strconv to a negative int64 (ignoring ErrRange), producing a wrong-sign value at the caller.
- nominalrequiredpresentCovered by 1 test
Behavior for unusual but valid input combinations.
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.
- 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 !getint_value_overflows_int64 | returns_getint_overflow_error
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| getint_value_overflows_int64 | — | True when GetInt addresses a JSON number token whose magnitude exceeds the int64 range. | |
| returns_getint_overflow_error | — | True when GetInt returns the documented overflow error for a value exceeding int64 range. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_076_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_076_Row2_InvariantViolationexercises 1 condition scenario
- TestMCDC_SYS_REQ_076_Row3_OverflowErrorexercises 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| # | getint_value_overflows_int64 | returns_getint_overflow_error | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | getint_value_overflows_int64 | |
| 2 | T | F | F | getint_value_overflows_int64 | |
| 3 | T | T | T | returns_getint_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)
- 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
Parent requirements (1)
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.