Plugable Auto-unpack subsystem

Open
#446 4 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no files, tests, or entry points. Start by reviewing the public API and examples for binary views and packed-binary handling. Done should be defined as separate views for the packed and post-packed binaries, with agreed behavior and coverage.

Written by the indexing model from the issue text.

Description

Component: Core Effort: High Impact: Medium

For packed binaries we should create separate binary views one for the packed and one for post-packed binary.

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

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.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.