Findings Quality: 19 tests: 19 passed, 0 failed, 0 skipped, 18 of 18 requirements proved, 0 open issues, 0 open tickets. The tests and issues of the libraryFindings: its three layers as namespaces.#Entry pointssrc/mod.tssrc/governance/mod.tssrc/logical/mod.tssrc/physical/mod.ts#Modulesgovernance/modThe Governance layer of Findings: what a finding is, as data.governance/modelWhat a finding is, whichever tool found it: a rule, a title, a severity, the asset it is about and where on it, a description, a way to fix it, the weaknesses (CWE) and vulnerabilities (CVE) it…logical/modThe Logical layer of Findings: the importers, the lifecycle and the controls.logical/resultWhat an importer gives: the findings, and what could not be read.logical/burpBurp Suite: the XML report (<issues>).logical/planningA finding is an item of Planning (commons planning 0037-planning), of its item kind finding: its life is the events of that item and its state is the fold of them, which is Planning's and not ours.logical/controlsThe controls of NIST SP 800-53 a finding is evidence against, from what it names: every finding bears on vulnerability monitoring (RA-5); one that names a vulnerability (CVE) or an outdated component…logical/nessusNessus: the .nessus XML export (NessusClientData_v2).logical/nmapNmap: the XML of -oX.logical/nucleiNuclei: the JSON lines of -jsonl.logical/sarifSARIF 2.1.0: every result of every run is a finding.logical/zapOWASP ZAP: the JSON report (-J, or the traditional JSON report).logical/detectWhich importer reads a report: by what is in it.physical/modThe Physical layer of Findings: reading report files.physical/filesReading report files: a file given by name must be a report an importer reads; a folder is walked, and a JSON or XML file in it that no importer reads is skipped without a word.