EFForg/rayhunter

enhance rayhunter-check output

Open

#570 opened on Aug 26, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Rust (431 forks)github user discovery
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (5,271 stars)
PR merge metrics
 (PR metrics pending)

Description

What problem does this feature solve or what does it enhance?

On device, rayhunter analyzes qmdl files and creates json formatted warning output files.

rayhunter-check can reanalyze those files, but seems to only support a plain text output format. Would it be possible to enhance rayhunter-check to output json formatted blobs which match rayhunter?

USE CASE:

I currently run a small git repo of "interesting" ray hunter traces. I'd like to enhance this repo to automatically parse files and create a wiki which looks roughly like the rayhunter webui. This would allow folks to see the files and warnings easily, and download the files for further research. This is all open source and done only for the purposes of helping the rayhunter project, I make zero dollars from this.

Proposed Solution

Make rayhunter-check output json formatted text.

In 'rayhunter-check -p' mode I would make a json file named after each parsed file, similar to how the on device parsing works.

Alternatives Considered

No response

Contributor guide