Code audit reports generated by Claude Code for open-source projects.
Each report was produced by a multi-agent static analysis pass over the full source tree, looking for bugs, panics, logic errors, performance issues, dead code, and architectural problems.
To see the report, you need to only download certain html file, and open it on your any web browser.
Help open-source maintainers find and fix real bugs - especially panics, logic errors, and other issues that are hard to spot during normal code review.
It contains some false positives, but also catches a large number of real problems.
You have two paths to help the open-source ecosystem:
- Validate findings and open issues for confirmed bugs in the project's repo
- Open pull requests for issues you have validated as correctly reported bugs
Some issues carry an "Easy" label, meaning the fix should be straightforward - a good place to start. For example, in the Wine codebase there is a bug that survived for 2 years unnoticed (many older bugs stay hidden from maintainers' view):
### CPY_36 `MEDIUM`
**Description:** In video_mixer_collect_output_types the output media-type height is computed from the geometric aperture using OffsetX instead of OffsetY (both width and height add aperture.OffsetX.value). Output render-target heights are wrong whenever the aperture has a non-zero vertical offset.
**Locations:**
"""
dlls/evr/mixer.c:780-781
780 | width = aperture.OffsetX.value + aperture.Area.cx;
781 | height = aperture.OffsetX.value + aperture.Area.cy;
"""
**Fix:** Change line 781 to: height = aperture.OffsetY.value + aperture.Area.cy;
As you can see, the issue comes pre-verified with a suggested fix.
In case of fixing big group of issues, I can easily generate a new report, to clarify, which problems were fixed and which not
ProjectName_YYYYMMDD.html
The date means when the report was generated.
Only the interactive HTML files are stored here (ProjectName_YYYYMMDD.html).
Each report has severity filters (critical / high / medium / low), type filters,
and a "Copy as GitHub Markdown" button on each finding for easy issue reporting.
find_reports.py gathers the audit output into this repo. It recursively searches a
source folder for findings-interactive.html files (the output of the code-audit pass)
and copies each one here under the canonical ProjectName_YYYYMMDD.html name.
python3 find_reports.py <source-folder> # e.g. python3 find_reports.py ~/test
How names are resolved:
- the project name is the directory that contains
___FINDINGS___(.../<Project>/___FINDINGS___/findings-interactive.html-><Project>), falling back to the file's own parent directory if there is no___FINDINGS___; - the date is the report file's modification time.
Per-project rules when copying:
- if an identical report is already here, it is left untouched (never overwritten);
- if only older version(s) exist, they are deleted and the newer report takes their place;
- if a newer version is already here, the older source report is skipped (no downgrade).