Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen ParseInt receives a syntactically well-formed integer token that does not overflow int64, the parser shall return the corresponding int64 value.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ParseInt receives a syntactically well-formed integer token that does not overflow int64, the parser shall return the corresponding int64 value.
the parser shall always satisfy !raw_int_token_is_well_formed | returns_parseint_value
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
ParseInt success on non-overflow integer tokens should be specified independently from overflow and malformed-token outcomes.
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
- human:buger · lead_engineer
- Reviewed
- Jul 26, 2026, 19:27 UTC
History
- Created
- Apr 13, 2026, 17:21 UTC · human:cli
- Modified
- Jul 26, 2026, 19:27 UTC · human:buger
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
3 obligations · 3 discharged
Browse the catalogueBehavior for unusual but valid input combinations.
ParseInt on a leading-zero canonical token like 007 returns 7 with the leading zeros stripped inconsistently, or off-by-one on a single-digit 0 token, producing wrong results for canonical-form inputs.
- nominalrequiredpresentCovered by 1 test
Behavior when inputs are syntactically or structurally invalid.
ParseInt on a sign-only token ("-") returns (0, nil) — silent false-success — instead of MalformedValueError, masking malformed input as a valid zero (DEFECT-260726-3F95 / KI-2).
- negativerequiredpresentCovered by 1 test
- nominalrequiredpresentCovered by 1 test
Behavior specified when inputs are nil, null, or zero-value.
ParseInt on a nil slice panics with index-out-of-range at data[0] in the first-byte classification instead of returning MalformedValueError.
- negativerequiredpresentCovered by 1 test
- 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_is_well_formed | returns_parseint_value
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| raw_int_token_is_well_formed | — | True when ParseInt receives a syntactically well-formed integer token that does not overflow int64. | |
| returns_parseint_value | — | True when ParseInt returns the corresponding int64 value. |
Witnesses· 3 scenarios total
- TestBytesParseIntbytes_test.go:107
- BenchmarkParseIntbytes_test.go:123
- BenchmarkParseIntUnsafeSlowerbytes_test.go:132
- BenchmarkParseIntOverflowsbytes_test.go:142
- FuzzParseIntNativefuzz_native_test.go:160
- TestMCDC_SYS_REQ_015_Row1_TriggerFalsemcdc_spec_witnesses_test.go:317exercises 1 condition scenario
- TestAdditionalFuzzHarnessCoveragemcdc_supplement_test.go:425
- TestObligation_SYS_REQ_015obligation_evidence_test.go:205
- TestParseIntparser_test.go:2360exercises 2 condition scenarios
- TestParseIntSignOnly_KI2parser_test.go:2447
- TestPropertyParseReferenceOracleproperty_test.go:255
- TestOracleParseIntreference_oracle_test.go:758
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.
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
Files to re-check (2)
- fuzz.gofuzz.go
- parser.goparser.go
Tests to re-run (8)
- bytes_test.gobytes_test.go
- fuzz_native_test.gofuzz_native_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- mcdc_supplement_test.gomcdc_supplement_test.go
- obligation_evidence_test.goobligation_evidence_test.go
- parser_test.goparser_test.go
- property_test.goproperty_test.go
- reference_oracle_test.goreference_oracle_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.