torvalds/linux audit
Delivery risk audit on GitHub · Analysed 11 Aug 2026 · GitHub
This delivery risk audit analyses the last 90 days of public commit history for torvalds/linux. It identifies files that concentrate bug-fix activity, measures revert frequency as a signal of release instability, and maps contributor spread to highlight knowledge concentration risk. The risk score weights bug-fix commits and reverts for each file, with higher scores indicating files that have required the most corrective attention in the analysed period.
Top Risk Files
| File | Risk | Bug Commits | Reverts | Commit touches |
|---|---|---|---|---|
| kernel/trace/ring_buffer.c | 60 | 6 | 0 | — |
| kernel/trace/ftrace.c | 50 | 5 | 0 | — |
| drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 30 | 0 | 2 | — |
| drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 30 | 0 | 2 | — |
| net/tls/tls_sw.c | 30 | 0 | 2 | — |
| tools/testing/selftests/net/tls.c | 30 | 0 | 2 | — |
| MAINTAINERS | 25 | 1 | 1 | — |
| kernel/trace/trace.c | 20 | 2 | 0 | — |
| Documentation/netlink/specs/ovpn.yaml | 15 | 0 | 1 | — |
| drivers/accel/amdxdna/amdxdna_gem.c | 15 | 0 | 1 | — |
| drivers/dibs/dibs_main.c | 15 | 0 | 1 | — |
| drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 15 | 0 | 1 | — |
| drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c | 15 | 0 | 1 | — |
| drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.h | 15 | 0 | 1 | — |
| drivers/gpu/drm/amd/amdgpu/amdgpu_lockdep.c | 15 | 0 | 1 | — |
| drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c | 15 | 0 | 1 | — |
| drivers/gpu/drm/amd/amdgpu/gfx_v12_0.c | 15 | 0 | 1 | — |
| drivers/gpu/drm/amd/amdgpu/gmc_v12_1.c | 15 | 0 | 1 | — |
| drivers/gpu/drm/amd/amdgpu/jpeg_v4_0_5.c | 15 | 0 | 1 | — |
| drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_0.c | 15 | 0 | 1 | — |
Other audited repositories
- facebook/react
- tlsnojokes-sudo/DPH-Classifieds_audit
- LiberoNuvola/PRE-RICH-scratch-and-win-game
- kubernetes/kubernetes
- denoland/deno
- opentofu/opentofu
- apache/kafka
- cilium/cilium
- helm/helm
- argoproj/argo-workflows
- istio/istio
- ansible/ansible
✨ AI Interpretation
Get a plain-English explanation of what these metrics may (and may not) mean for delivery risk.
View interactive reportWhat does your private codebase look like?
This analyses public commit history. Connect a private repo to see bug-fix hotspots, ownership risk and delivery friction on the code your team ships every day. Read-only, no source code stored.
Audit your private repo, free →