Skip to content

[New Plugin]: Rust Metadata Carver #367

Closed

Description

@cxiao

Plugin Description

Hello! This is a new Binary Ninja plugin to find metadata from Rust binaries. Right now, it just finds source file locations from Rust panic location metadata, and labels all cross references to these source file locations with tags.

I've had it written for a while, but never submitted it to the community plugin repo until now. Screenshots below:

Image Image

Plugin Repository URL

Repo URL: https://github.com/decoderloop/rust_metadata_carver

Real Release

  • I have made a real release

Creation and Validation of plugin.json

  • I have created a valid plugin.json file

Activity

  1. psifertex commented on Aug 5, 2026

    @psifertex
    Member

    Sorry for the delay, added!

  2. cxiao commented on Aug 7, 2026

    @cxiao
    Author

    Thanks @psifertex! I did notice some issues with the plugin metadata, though, in the version of the plugin that's published on the plugin repository. The plugin metadata seems to be different there than what I published in my release here: https://github.com/decoderloop/rust_metadata_carver/blob/v1.0.0/plugin.json

    • The version of the plugin on the plugin repository seems to be missing the api specifier, i.e. this part in plugin.json:
      "api": [
        "python3"
      ],
    

    This means that attempting to install the plugin gives the following warning:

    Image

    And after force installation, the plugin fails to load due to the supported apis list being empty:

    [Plugin Repository: community] Failed to find plugin loader for installed plugin.
    [Plugin Repository: community] Plugin supports apis: [] but the only ScriptingProviders available are [python3, debugger, target]
    [Plugin Repository: community] Failed to load plugin: rust_metadata_carver
    
    • The version of the plugin on the plugin repository seems to have both helper and platform listed, whereas the original plugin.json only has helper.

    Could you take a look and ensure that the plugin.json as published is correct? Let me know if you need anything on my end as well.

  3. psifertex commented on Aug 21, 2026

    @psifertex
    Member

    Sorry about that, I think the error is on my side and is fixed!

  4. cxiao commented on Aug 21, 2026

    @cxiao
    Author

    Thanks @psifertex! Looks fixed from my end now too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions