what is fivem-resource-scanner fr?

FiveM Resource Security Scanner is a free tool that checks Lua scripts written for FiveM and RedM, the multiplayer modification frameworks for Grand Theft Auto V, for hidden backdoors before you install them on your game server. It only reads the code, it never runs it, so it is safe to point at a script you do not trust yet. Backdoored FiveM scripts are a genuine problem in that community: hidden code can grant an attacker admin access to your server, steal player data such as IP addresses and Discord tokens, or quietly install a crypto miner on the machine hosting your server. Many existing free scanners work by matching simple keywords, which tends to flag large portions of normal, harmless scripts and trains people to ignore the warnings. This scanner tries to reduce that noise in a few ways. It only treats a network request as suspicious data exfiltration when it targets an unfamiliar domain and the script also reads player identifiers or tokens nearby, so an ordinary request to a known service is not flagged. It also looks at how random or scrambled a chunk of text appears, which helps catch obfuscated or encoded payloads that plain keyword searches miss, and it automatically decodes hex and base64 strings so you can see what a hidden URL or command actually says. Code inside comments does not trigger findings, and well-known FiveM hosting domains are allowed by default. Running it requires only Python, with no extra packages to install, and it works on Windows, Linux, or macOS. On Windows, you can simply drag a resource folder onto a batch file and it scans, prints results, and opens a readable HTML report in your browser automatically. From a terminal, you point it at one resource folder or your whole resources directory, with an option to only show serious findings. Every finding lists a severity level, the exact file and line, and an explanation of why it matters, ending in an overall verdict from likely clean up to danger. The project is honest about its limits: a clean scan result does not prove a script is safe, and it cannot see through heavy custom obfuscation or a payload address computed only while the script is running. It is meant as one layer of review alongside checking an author's reputation, not a guarantee by itself.