Security fixes go into the latest release. Upgrade with cargo install rust-anything or
npm i -g rust-anything before reporting, in case it is already fixed.
| Version | Supported |
|---|---|
| Latest minor (1.x) | Yes |
| Older | No |
Please report it privately, not in a public issue: use Report a vulnerability on the repository's Security tab.
Include what you found, how to reproduce it, which version and platform you used, and what an attacker could do with it. You'll get a reply within a few days, and you'll hear when a fix is out. If you'd like credit in the release notes, say how you want to be named.
rust-anything runs your code on purpose. record, diff, app record and app replay execute
the original app and the Rust port to compare them, so running them on an untrusted repository is
like running that repository yourself. That alone is not a vulnerability.
These are in scope:
- Code that rust-anything generates (bindings, drivers, front doors) with memory-unsafe or undefined behavior that the port didn't ask for.
- Reading or writing files outside the project, the crate and the system temp folder.
- A crafted recording (
cases.jsonl,rust/app-cases/) that makes rust-anything run commands it wasn't told to run. - The release pipeline: the published binaries, the npm package or the crates.io crate not matching the tagged source.
- The MCP server doing more than the tool call asked for.
Once a fix is released, the advisory is published with credit to the reporter, unless they prefer otherwise.