Proof Portal
jsonparser
ProbeLabs23 findings · 123 requirementsThe fastest JSON parser for Go — formally verified with ReqProof (real library, master).
When Delete is called without a path, the parser shall return an empty document.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When Delete is called without a path, the parser shall return an empty document. DeleteFound is the explicit-found variant of Delete: DeleteFound(data, keys...) returns (result, found) where result is the post-deletion document (or the original input when the path is missing) and found is true iff the addressed value was located and removed.
the parser shall always satisfy delete_path_is_provided | delete_returns_empty_document_without_path
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
Delete without a path is a distinct API outcome and should not be bundled with successful deletion, missing-target handling, or malformed-input robustness.
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
- Jul 26, 2026, 20:26 UTC
History
- Created
- Apr 13, 2026, 17:15 UTC · Created via CLI
- Modified
- Jul 26, 2026, 20:26 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.
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.
3 obligations · 3 discharged
Browse the catalogueBehavior when inputs are absent, nil, zero-length, or blank.
Delete with no path returns a non-empty document instead of an empty one, leaking data the caller explicitly asked to erase.
- nominalrequiredpresentCovered by 1 test
Behavior when inputs are syntactically or structurally invalid.
Delete on a well-formed array/object with whitespace between the deleted element and the trailing comma (or the close bracket) leaves a dangling comma or close-bracket sequence in the output, producing malformed JSON the caller cannot re-parse (DEFECT-260726-3PSJ, found by FuzzPathMutation).
- negativerequiredpresentCovered by 1 test
- nominalrequiredpresentCovered by 1 test
Behavior specified when inputs are nil, null, or zero-value.
Delete on nil data panics in nextToken at data[0] instead of returning the empty document, crashing the caller on a nil trust-boundary input.
- 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 delete_path_is_provided | delete_returns_empty_document_without_path
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| delete_path_is_provided | — | True when Delete is called with at least one path segment. | |
| delete_returns_empty_document_without_path | — | True when Delete returns an empty byte slice because no path segment was provided. |
Witnesses· 3 scenarios total
- TestFuzzDeleteHarnessCoverageexercises 1 condition scenario
- TestMCDC_SYS_REQ_010_Row1_NoPathNoEmptyexercises 1 condition scenario
- TestDeleteexercises 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| # | delete_path_is_provided | delete_returns_empty_document_without_path | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | F | delete_path_is_provided | |
| 2 | F | T | T | delete_returns_empty_document_without_path | |
| 3 | T | F | T | delete_path_is_provided |
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 (7)
- coverage_closure_test.gocoverage_closure_test.go
- dead_code_audit_test.godead_code_audit_test.go
- issues_56_107_229_test.goissues_56_107_229_test.go
- obligation_evidence_test.goobligation_evidence_test.go
- parser_test.goparser_test.go
- set_spec_test.goset_spec_test.go
- v131_regression_test.gov131_regression_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.