Scantide
Experimental filename intelligence search

Find where a filename
appears in the evidence.

Enter a filename such as log4j-core.jar, openssl.dll or jquery.min.js, with an optional version. Scantide searches inside CVE and advisory documents for the complete filename first. If the extension is omitted in source text, a separate related-component tier may match the complete filename stem. Individual broad tokens are never used.

Exact filename mentions are shown first. When a version is supplied, records containing both the filename and that version are ranked first; filename-only records remain visible as context.
POC coverage note: Deep Search examines bounded portions of active CVE, advisory and CIRCL OSINT document collections and matches text inside selected evidence fields rather than Redis keys. It may miss references because of indexing, naming differences, compressed or unparsed content, search limits or source coverage. An exact match means the complete filename appeared in source text. When a version is supplied, a version match means that version string also appeared somewhere in the same source record; it does not by itself prove that the version belongs to that filename or is affected. CIRCL context linked through a CVE is shown separately and is not counted as a filename match. Repeated CIRCL sightings that resolve to the same canonical article or equivalent evidence are collapsed into one source entry with an observation count. A related-component match means only the complete filename stem appeared; it does not prove that the file is installed, vulnerable or applicable to a particular system.