For researchers

Cite BootIntel.

If you use BootIntel in a paper, thesis, dissertation, or technical report, use one of the references below. The methodology is documented on the coverage page (confidence labels, CVE match types, honest limitations).

BibTeX

@misc{bootintel_2026,
  title  = {{BootIntel}: Boot log analysis for embedded devices},
  author = {{Zenofex LLC}},
  year   = {2026},
  month  = {july},
  url    = {https://bootintel.com/},
  note   = {Accessed: YYYY-MM-DD}
}

Replace the YYYY-MM-DD in the note field with the date you actually accessed the tool.

APA (7th edition)

Zenofex LLC. (2026). BootIntel: Boot log analysis for embedded devices [Web application]. https://bootintel.com/

IEEE

Zenofex LLC, "BootIntel: Boot log analysis for embedded devices," 2026. [Online]. Available: https://bootintel.com/. [Accessed: DD-Mmm-YYYY].

Reproducible-research checklist

+Sample corpus: 31 real boot logs are published at /samples/bootintel-N.txt (N=1..30 plus bootintel.txt). Immutable public URLs with 1-year cache, safe to hotlink from a paper's supplementary materials.
+Sample analysis output: real PDF report at /samples/example-report.pdf generated by the production pipeline from bootintel-15.txt (TP-Link TL-WR841N v8). Includes per-finding evidence citations and CVE match provenance.
+Confidence labels: Confirmed / Probable / Weak, defined on /coverage. Match types: Exact version / Affected range / Component / Masked preview.
+Known limitations: documented explicitly on /coverage. Suitable to paraphrase into a threats-to-validity section.
+Structured export: Researcher tier and above unlocks GET /api/scans/{id}/report.json for machine-readable analysis output. Includes schema version (bootintel_schema: scan-report/v1) so downstream tooling can pin.
+CVE data source: matched against the U.S. National Vulnerability Database (NVD) CVE feed with daily sync.

Contact for research use

Working on a paper that uses BootIntel? If you need a dataset excerpt, a versioned methodology footnote, or help scoping what to cite, email [email protected] with the paper's title, target venue, and use case.

A formal DOI and versioned methodology PDF are on the roadmap; if you need one for a submission deadline, ask.