Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen ParseBoolean receives a partial boolean literal (e.g., "tru", "fals", "t", "f"), the parser shall return MalformedValueError because the token does not match either "true" or "false" exactly.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When ParseBoolean receives a partial boolean literal (e.g., "tru", "fals", "t", "f"), the parser shall return MalformedValueError because the token does not match either "true" or "false" exactly.
the parser shall always satisfy !raw_boolean_literal_is_partial | returns_error_for_partial_boolean_literal
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Partial boolean literals are a distinct malformed-input subclass that exercises the bytes.Equal comparison boundary. Truncated network payloads commonly produce these.
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: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.
1 obligation · 1 discharged
Browse the catalogueParseBoolean on a 3-byte tru over-reads 4 bytes past EOF checking for the true/false literal, panicking with index-out-of-range on a buffer that is exactly 3 bytes long.
- 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_boolean_literal_is_partial | returns_error_for_partial_boolean_literal
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| raw_boolean_literal_is_partial | — | True when ParseBoolean receives a partial boolean literal such as "tru" or "fals". | |
| returns_error_for_partial_boolean_literal | — | True when ParseBoolean returns MalformedValueError for a partial boolean literal. |
Witnesses· 3 scenarios total
- TestParseBooleanPartialLiteralsdeep_spec_test.go:489
- TestMCDC_SYS_REQ_057_Row1_TriggerFalsemcdc_spec_witnesses_test.go:2016exercises 1 condition scenario
- TestMCDC_SYS_REQ_057_Row2_InvariantViolationmcdc_spec_witnesses_test.go:2028exercises 1 condition scenario
- TestMCDC_SYS_REQ_057_Row3_PartialErrormcdc_spec_witnesses_test.go:2036exercises 1 condition scenario
- TestObligation_SYS_REQ_057obligation_evidence_test.go:464
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 (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.