Automotive cybersecurity threat reports
One report for every public GitHub repository about automotive cybersecurity: diagnostic tools, protocol stacks, fuzzers, firmware and research code. Each report rates how much of a threat the repository poses to vehicles.
This site collects those reports and lets you see where the risk is concentrated, so you can decide which ones to read first.
–repositories analysed
–critical or high
–attack surfaces
–repository owners
Where to start
Threat overview
The totals, the ten reports to read first, and a searchable list of all of them.
Threat views
Risk per attack surface, surfaces that appear together, the second model’s opinion, owners, and attack tools versus defences.
How to read a rating
Every report carries three things.
- Threat level
- How serious the repository looks, from low to critical.
- Critical
- Read these first.
- High
- Serious, and worth a careful read after the critical ones.
- Medium
- Relevant, but usually something to plan rather than rush.
- Low
- Little direct risk on its own.
- Second opinion
- A second model reviews the first model’s rating. When it disagrees, its verdict becomes the final rating. When it gives no verdict, the first rating stands.
- Attack surfaces
- The parts of a vehicle the repository touches, such as UDS diagnostics, ISO-TP, DoIP or ECU firmware. A repository can touch several.
All pages
- Threat overviewTotals, priority list and full table.
- Threat viewsFive ways to slice the same data.
- Threat-score heatmapEvery repository on one map. Click one to open its report.
- Attack surface atlasRepositories listed per attack surface.
- Attack surface clustersRepositories grouped by similar surfaces.
- Protocol-threat matrixWhich protocols carry which threats.
- Dashboard with menuThe older views side by side in one frame.