Vector35 / Vector35/binaryninja-api
Project-specific signature libraries and plugins
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
We were not able to completely implement every Projects feature we wanted before getting it merged to dev yesterday.
This issue is for adding the ability for projects to have project-specific signature libraries and plugins that are available to all other files within the project.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Projects feature merged to the dev branch and its existing project APIs. The issue names no files, tests, or entry points; completion would require defining how project-specific signature libraries and plugins become available to every file in a project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100