Proof Portal
jsonparser
ProbeLabsviewing a historical runThe fastest JSON parser for Go — formally verified with ReqProof (real library, master).
When GetString is called with a nil byte slice as input, the parser shall return an empty string and an error or not-found result without panicking.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When GetString is called with a nil byte slice as input, the parser shall return an empty string and an error or not-found result without panicking.
the parser shall always satisfy !getstring_input_is_nil | getstring_returns_safe_result_for_nil
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Nil input must not cause a nil-pointer dereference. GetString delegates to Get, so nil safety must be preserved through the delegation chain.
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
- Leonidbugaev
- Reviewed
- Apr 21, 2026, 00:00 UTC
History
- Created
- Apr 21, 2026, 00:00 UTC · Claude · AI agent
- Modified
- Jul 26, 2026, 13:17 UTC · Created via CLI
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
Every recorded revision of this object's source — newest first, each with the commit message and its file-level diff.
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
The tests that discharge each obligation aren't available for a historical run
The evidence matrix behind each obligation comes from the live audit index, which can't be rebuilt for a past commit. Nothing here means unknown — not that the requirement has no obligations.
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 !getstring_input_is_nil | getstring_returns_safe_result_for_nil
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| getstring_input_is_nil | — | True when GetString is called with a nil byte slice as input. | |
| getstring_returns_safe_result_for_nil | — | True when GetString returns an empty string and error without panicking for nil input. |
Witnesses· 3 scenarios total
- TestMCDC_SYS_REQ_091_Row1_TriggerFalseexercises 1 condition scenario
- TestMCDC_SYS_REQ_091_Row2_InvariantViolationexercises 1 condition scenario
- TestGetStringNilSafetyexercises 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| # | getstring_input_is_nil | getstring_returns_safe_result_for_nil | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | getstring_input_is_nil | |
| 2 | T | F | F | getstring_input_is_nil | |
| 3 | T | T | T | getstring_returns_safe_result_for_nil |
Its place
This requirement inside its trace neighbourhood — authored trace links only; automatically derived links come from the audit index and aren't shown here.
Loading graph…
Trace evidence
The concrete artifacts linked to this requirement — implementing code, verifying tests, documents, and the findings raised against it.
No findings affect this requirement
Nothing was flagged against this requirement in the pinned run.
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
Tests to re-run (2)
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- obligation_property_test.goobligation_property_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.