How many pinned upstream parser IDs have a native Keryn importer with verified fixtures?
| Evaluation detail |
Description |
| Keryn engine |
Keryn native report importers at f999939f2701 |
| Reference |
DefectDojo pinned parser inventory and fixture expectations |
| Corpus |
All parser IDs in the pinned DefectDojo tree, restated from crates/dd/generated/upstream-parser-status.json |
| Comparison |
A parser ID is fixture-verified when the landed native adapter passed all pinned packet fixtures and its available extracted upstream count assertions. Unported and unverified IDs stay in the denominator. |
| Receipt |
defectdojo-passive-importers.json, sha256 c0d4ff616bf455d3 |
| Measure |
Value |
Count |
Denominator |
| Complexity bands fully fixture-verified |
0% |
0 / 3 |
all upstream complexity bands |
| Upstream parser IDs with fixture-verified native importers |
42.0% |
107 / 255 |
all parser IDs in the pinned DefectDojo tree |
Cases by status: 3 differs.
- Coverage is native offline report parsing against pinned fixtures and available upstream expectations.
- The Django application did not serve as a live differential oracle. Schema field parity, live scanning and parity beyond the pinned fixtures remain unverified.
- Coverage mixes the full population of upstream parser IDs and fixture runs from verified adapters. Reused fixture files can contribute more than one run.
| Case |
Status |
Reference rows |
Keryn rows |
Matching |
Missing |
Extra |
complex |
differs |
|
|
|
|
|
medium |
differs |
|
|
|
|
|
simple |
differs |
|
|
|
|
|
Show every case
| Case |
Status |
Reference rows |
Keryn rows |
Matching |
Missing |
Extra |
complex |
differs |
|
|
|
|
|
medium |
differs |
|
|
|
|
|
simple |
differs |
|
|
|
|
|