Vector35 / Vector35/binaryninja-api

Display what Enterprise user caused a given change

Open
#6,354 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: Core Component: Database Component: UI Edition: Ultimate Effort: Medium Impact: Medium
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

What is the feature you'd like to have?
Customers that are collaborating really want to see which user (if any) provided certain information, or touched things last. So, in addition to something like #2275 (on which this feature may block, I'm not sure) that will show things like "this symbol came from analysis" or "this symbol came from this specific type library", Enterprise users want things like "...and fuzyll pushed the snapshot in which this was touched last".

Is your feature request related to a problem?
You know how git blame is really cool for figuring out who on your team you should slap silly speak with about a past change? Same deal.

Are any alternative solutions acceptable?
Not married to any specific internal implementation or representation, and I don't have a firm idea of how this should be displayed in the UI. So, many alternative solutions are probably acceptable. We just need to surface the information if we've got it.

Additional Information:
Migrated here from an internal Enterprise issue tracker.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Begin by locating the existing analysis or type-library provenance data and the Enterprise UI that displays snapshot changes; determine whether user attribution is already stored. Done means agreeing on a display location and surfacing the Enterprise user, when available, for the relevant change.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, git
Domain
reverse-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.