An open, vendor-neutral standard for verifying open-source intelligence. OOVS v0.1.0 defines ten testable requirements published simultaneously as normative text and machine-readable data, with one acceptance test per requirement, a portable assessment schema, and continuous validation.
Open an issue in the repository for questions, requirement feedback, or implementation reports.
Security and safety concerns follow SECURITY.md. Conduct concerns follow the OWASP reporting path described in CODE_OF_CONDUCT.md.
Do not include personal data, live-case material, victim information, target lists, credentials, or operationally sensitive detail in any public channel.
Project Leader
Project leader for the OWASP Open Source Intelligence Standard. Designed the OOVS assurance baseline and the specification-as-code pipeline that keeps its normative text, machine-readable requirements, acceptance tests, and hash-pinned release manifests provably consistent in continuous integration. Interests: OSINT verification, provenance and source-origin independence, attribution, and accountable use of AI in analytic workflows.