THE fastest alternative JSON parser for Go that does not require schema
This report summarizes scanner evidence for buger/jsonparser, a Go project with 5,662 GitHub stars. SynthScan examined 55,138 lines of code across 265 source files, recording 114 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 2.3 (Low pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.
Can maintainers explain intent, assumptions, and trade-offs? 114 finding(s).
Are imports declared and package/API names verified? 0 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 114 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 114 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | obligation_evidence_test.go | 1 | package jsonparser | COMMENT |
| LOW | json_fuzz_test.go | 1 | // Structure-aware JSON fuzzer for the jsonparser public surface. | COMMENT |
| LOW | json_fuzz_test.go | 21 | // 3. ROUND-TRIP — Get(out, path) returns the set value. | COMMENT |
| LOW | json_fuzz_test.go | 501 | *buf = append(*buf, '\\', 'u', | COMMENT |
| LOW | json_fuzz_test.go | 1061 | return false | COMMENT |
| LOW | json_fuzz_test.go | 1361 | // valid and the path shape matches the container type at every | COMMENT |
| LOW | json_fuzz_test.go | 1501 | // | COMMENT |
| LOW | json_fuzz_test.go | 1521 | // When the fuzz engine mutates data into non-JSON garbage (or ~30% | COMMENT |
| LOW | json_fuzz_test.go | 1561 | if r.Intn(5) == 0 { // 20% chance | COMMENT |
| LOW | optimization_bench_test.go | 1 | package jsonparser | COMMENT |
| LOW | escape.go | 21 | // untranslated, so no lemma is attached here. | COMMENT |
| LOW | escape.go | 41 | // r := h2I(c) | COMMENT |
| LOW | escape.go | 101 | // | COMMENT |
| LOW | escape.go | 121 | COMMENT | |
| LOW | escape.go | 141 | // Lone high surrogate (0xD800-0xDBFF): the high-surrogate escape is not | COMMENT |
| LOW | escape.go | 261 | COMMENT | |
| LOW | optimization_equiv_test.go | 1 | package jsonparser | COMMENT |
| LOW | mcdc_spec_witnesses_test.go | 1 | package jsonparser | COMMENT |
| LOW | mcdc_spec_witnesses_test.go | 21 | // - Invariant-violation rows (formula evaluates FALSE in the table) are | COMMENT |
| LOW | parser_test.go | 1381 | return | COMMENT |
| LOW | parser_test.go | 1401 | // MCDC SYS-REQ-021: N/A | COMMENT |
| LOW | parser_test.go | 1861 | { | COMMENT |
| LOW | parser_test.go | 2361 | // MCDC SYS-REQ-040: raw_int_token_is_well_formed=F, raw_int_token_overflows_int64=F, returns_parseint_malformed_error=T | COMMENT |
| LOW | mcdc_supplement_test.go | 421 | }) | COMMENT |
| LOW | mcdc_supplement_test.go | 661 | } | COMMENT |
| LOW | mcdc_supplement_test.go | 761 | count++ | COMMENT |
| LOW | encoding_json_fuzz_test.go | 1 | // Differential fuzzer targeting Go's official encoding/json package. | COMMENT |
| LOW | encoding_json_fuzz_test.go | 21 | // encoding/json. encoding/json is treated as the reference oracle. Any | COMMENT |
| LOW | encoding_json_fuzz_test.go | 161 | COMMENT | |
| LOW | encoding_json_fuzz_test.go | 221 | // sides, so DeepEqual still holds. This is the spec-literal gate. | COMMENT |
| LOW | encoding_json_fuzz_test.go | 321 | // error are both acceptable. Only a panic is a failure. | COMMENT |
| LOW | encoding_json_fuzz_test.go | 381 | } | COMMENT |
| LOW | encoding_json_fuzz_test.go | 421 | }) | COMMENT |
| LOW | encoding_json_fuzz_test.go | 541 | // | COMMENT |
| LOW | encoding_json_fuzz_test.go | 641 | // FuzzEncodingJSON is the structure-aware differential fuzzer for | COMMENT |
| LOW | mcdc_code_supplement_test.go | 1 | package jsonparser | COMMENT |
| LOW | coverage_closure_test.go | 1 | package jsonparser | COMMENT |
| LOW | coverage_closure_test.go | 101 | // already covered by TestDelete. Rows 1 and 3 need explicit witnesses. | COMMENT |
| LOW | path_fuzz_test.go | 1 | // Path-mutating fuzzer for the jsonparser public surface. | COMMENT |
| LOW | path_fuzz_test.go | 21 | // (1) No-panic invariant. The fuzz body uses the recover-and-record | COMMENT |
| LOW | path_fuzz_test.go | 101 | "stack": string(stack), | COMMENT |
| LOW | path_fuzz_test.go | 241 | } | COMMENT |
| LOW | path_fuzz_test.go | 381 | // | COMMENT |
| LOW | path_fuzz_test.go | 401 | // mismatches (e.g. path "a.[0].[1]" where `a.[0]` resolves to an OBJECT | COMMENT |
| LOW | path_fuzz_test.go | 461 | } | COMMENT |
| LOW | path_fuzz_test.go | 601 | case 1: | COMMENT |
| LOW | reference_oracle_test.go | 1 | // Reference-oracle property tests for the jsonparser public surface. | COMMENT |
| LOW | reference_oracle_test.go | 21 | // All generators are independent of the parser under test (they build JSON | COMMENT |
| LOW | reference_oracle_test.go | 41 | // the RAW bytes from the input. The Get test compares canonicalized | COMMENT |
| LOW | reference_oracle_test.go | 61 | // D7. KNOWN BUG — Set with nested out-of-range array index silently | COMMENT |
| LOW | reference_oracle_test.go | 81 | // when (a) the path's full lookup misses, (b) a subpath resolves to | COMMENT |
| LOW | reference_oracle_test.go | 601 | if knownBugPaths+knownBugPanics > 0 { | COMMENT |
| LOW | property_test.go | 1 | // Property-based tests for the jsonparser core surface. | COMMENT |
| LOW | parser.go | 21 | OverflowIntegerError = errors.New("Value is number, but overflowed while parsing") | COMMENT |
| LOW | parser.go | 41 | // return tokenEnd(data) >= 0 | COMMENT |
| LOW | parser.go | 181 | // | COMMENT |
| LOW | parser.go | 221 | // } | COMMENT |
| LOW | parser.go | 261 | // | COMMENT |
| LOW | parser.go | 301 | func stringEndConfig(_ Config, data []byte, quote byte) (int, bool) { | COMMENT |
| LOW | sys_req_110_111_witness_test.go | 1 | package jsonparser | COMMENT |
| 44 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | parser.go | 1944 | // Step 1: find the next key | COMMENT |
| LOW⚡ | parser.go | 1982 | // Step 2: skip the colon | COMMENT |
| LOW⚡ | parser.go | 1991 | // Step 3: find the associated value, then invoke the callback | COMMENT |
| LOW⚡ | parser.go | 2000 | // Step 4: skip over the next comma to the following token, or stop if we hit the ending brace | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | parser.go | 1944 | // Step 1: find the next key | COMMENT |
| LOW⚡ | parser.go | 1982 | // Step 2: skip the colon | COMMENT |
| LOW⚡ | parser.go | 1991 | // Step 3: find the associated value, then invoke the callback | COMMENT |
| LOW⚡ | parser.go | 2000 | // Step 4: skip over the next comma to the following token, or stop if we hit the ending brace | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | json_fuzz_test.go | 1627 | // Generous (5s) so the gate is robust on slow CI; tight enough that an O(n²) | COMMENT |
| MEDIUM | proof.yaml | 48 | # oracle, fuzz-harness coverage) so `proof audit` stays fast on every | COMMENT |