Files

Dynamic instrumentation toolkit for developers, reverse-engineers, and security researchers. Learn more at frida.re.

Where things live

Organization What's there
frida Frida itself: the runtime, tools, language bindings, and the Luma GUI
frida-packages Packages you build on: runtime bridges, agent tooling, Node.js compatibility modules
frida-forks Patched forks of third-party projects. Not a list of things Frida needs
frida-labs Experiments, demos, and conference material

Main repositories

  • frida: releases, and the umbrella repository tying them together
  • frida-gum: instrumentation engine and the GumJS runtime
  • frida-core: injection, sessions, and the compiler
  • frida-tools: CLI tools such as frida, frida-trace, and frida-pm
  • luma: the Frida GUI

Language bindings: Python · Node.js · Swift · Go · Rust · .NET · QML · Pharo · Browser

Building from source

Clone the repository you want and run make. Run ./configure first to pick options or to cross-compile. Dependencies are fetched through Meson wraps, so a language binding like frida-python pulls in frida-core by itself.

For frida-server, frida-portal, frida-inject, frida-gadget, and the other binaries, clone frida-core and run make.

Out-of-tree builds work like autotools: run the repository's configure from the build directory you want. Run from the repository root, it uses ./build.