Frida vs Refinery

Frida is a dynamic instrumentation toolkit for developers, reverse-engineers, and security researchers. It lets users place scripts in running processes to hook functions, inspect APIs, and trace application code without source code. Documented uses include API tracing, diagnostics, encrypted-protocol analysis, and black-box testing.

Frida supports injected, embedded, and preloaded instrumentation. When injection is unavailable, Frida Gadget can be embedded in a program, including on jailed iOS and Android systems. Supported targets include Windows, macOS, GNU/Linux, iOS, watchOS, tvOS, Android, FreeBSD, and QNX. Language bindings include Node.js, Python, Swift, .NET, Qt/Qml, and Go, alongside a C API. The CLI tools require Python and run on Windows, macOS, or GNU/Linux; the documented installation command is `pip install frida-tools`.

Refinery is a free, MIT-licensed SQL migration toolkit for Rust applications. It runs migrations against a database connection supplied by the application, either from embedded Rust code or through the refinery_cli command-line tool. Migrations can be SQL files or Rust modules whose migration function returns a String. Refinery records applied versions and metadata, then checks for missing or divergent migrations before running unapplied work. By default, each migration runs in its own transaction; grouped mode can place all migrations in one transaction. Migrations can also be built into a binary, so separate files are not needed at deployment. Listed drivers include postgres, tokio-postgres, mysql, mysql_async, rusqlite, and tiberius; SQLx can be used with a Config implementing Migrate. Driver selection is handled through features. Maintainers describe limited capacity to maintain additional drivers and point to external repositories, naming Klickhouse as an example. Refinery aims to support stable Rust, the previous Rust version, and nightly. To reverse a migration, users must create another migration with the reversing changes.