flare-floss/scripts
lakshit verma 67fc76e4e4
build_oss_db: derive default output dir from data_root
The default --output-dir hardcoded a path constructed from parents[2],
duplicating the floss/tags/data root that data_root() already provides.
Use data_root() / "oss" so the script follows the same source of truth
as query_string.py.
2026-08-13 16:06:51 +05:30
..
analysis feat: migrate CLI flags and add runtime metrics 2026-08-11 18:27:28 +05:30
disassemblers Simplify disassembler script usage examples 2026-07-17 01:30:10 +05:30
tags build_oss_db: derive default output dir from data_root 2026-08-13 16:06:51 +05:30
__init__.py
README.md fix: harden default layout path and clean quantum leftovers 2026-07-29 00:25:24 +05:30

FLOSS Scripts

Auxiliary scripts live under scripts/, grouped by purpose:

Directory Purpose
disassemblers/ Convert classic FLOSS JSON output into import scripts for Binary Ninja, Ghidra, IDA Pro, Radare2, and x64dbg; includes the IDA plugin
tags/ Build and maintain FLOSS tag databases (global prevalence, OSS libraries, VT feeds)
analysis/ Batch analysis helpers

disassemblers/

Turn FLOSS JSON (floss -j sample.exe > results.json) into tool-specific artifacts.

  1. Run a render script, redirecting stdout to a file.
  2. Import or run the generated artifact in the target tool.

Example (Ghidra):

$ python render-ghidra-import-script.py results.json > apply_floss.py

See disassemblers/ for per-tool scripts and the IDA plugin (File → Script file… in IDA Pro).

Install FLOSS from source first; see installation.

tags/

Scripts that extract strings, build tag databases, and query them. See tags/README.md for the full pipeline.

analysis/

  • bulk_analyze.py — run floss over every binary in a directory and write JSON results.

Language-specific data maintenance (for example regenerating the Rust version hash database) lives alongside the implementation under floss/language/.