Asterpath · Revision 4
Supporting evidence
Triage unused-code candidates before calling them defects.
Twelve fictional candidates become four cleanup items after entry-point and generated-code review.
Fictional, not a scanner result. FICTIONAL ILLUSTRATIVE SAMPLE. Asterpath, its product, evidence, findings and measurements are invented. No Asterpath application was inspected and no scanner was executed. These are original GadirLabs illustrations, not native vendor exports.
What the fictional evidence shows
| Triage stage | Illustrative count | Interpretation |
|---|---|---|
| Scanner candidates | 12 | Unreviewed suggestions, not twelve confirmed defects. |
| Legitimate entries / false positives | 8 | Dynamic or generated entry points explain these candidates. |
| Confirmed unused exports | 4 | Cleanup opportunities with no demonstrated launch impact. |
| New material findings | 0 | The report's total remains eight. |
What it means
The configuration and entry-point model determine what the analysis can see. A warning count needs manual interpretation before deletion or a severity judgement.
What would establish a fix
In a real engagement, retain the exact configuration and native report, confirm each candidate, and rerun the relevant checks after any approved cleanup.
This page and its JSON are two views of the same original illustration. They are not separate findings or independent corroboration. A real client record would identify actual versions, inputs, outputs and evidence limits.